3.12.7: adding aufs support from git.code.sf.net/p/aufs/aufs3-standalone

[ghost]

NOTE: IT IS IMPORTANT TO REVIEW THE CHANGES to mm/fremap.c carefully, because the automatic patch of this file failed. See below and https://altiscale.atlassian.net/browse/OPS-2746

Followed the process in this script for doing the merge:

• https://github.com/VertiCloud/dev-homes/blob/master/dineshs/alexie/includes/scripts/upgrade-prometheus.sh

Failed merge:

$ cat fremap.c.rej 
--- mm/fremap.c
+++ mm/fremap.c
@@ -207,11 +207,12 @@
         */
        if (mapping_cap_account_dirty(mapping)) {
            unsigned long addr;
-           struct file *file = get_file(vma->vm_file);
+           struct file *file = vma->vm_file;

+           vma_get_file(vma);
            addr = mmap_region(file, start, size,
                    vma->vm_flags, pgoff);
-           fput(file);
+           vma_fput(vma);
            if (IS_ERR_VALUE(addr)) {
                err = addr;
            } else {

[dineshs-altiscale]

The kernel panics for me. Its likely config related rather than the simple/harmless change in fremap.c.

We need to hand-make the config, ensure it works and check it in. Where is the current kernel config used for this build?

[ghost]

For the record... We needed to change the kernel version produced by our build process to get the kernel working. The kernel config is in our internal tools repo (under packages/linux-stable), and is released internally and to customers as part of the src package. We're keeping the config file in a private repo, because that's consistent with Altiscale's other build and release processes, not because we want to hide it. I'd be happy to provide the config file to folks outside the company upon request, and would consider making it available in a public repo if that's important to anyone.