11961 2017-08-21 13:10:15 +0000 [linux-yocto] Build error with aufs 2017-09-19 16:22:15 +0000 1 1 7 Build System, Metadata & Runtime OE-Core kernel 2.3.1 x86 x86 RESOLVED FIXED Medium normal 2.4 M4 1 s.kumar.bdc11 bruce.ashfield akuster tom.zanussi --- --- Don't know oldest_to_newest 76028 0 s.kumar.bdc11 2017-08-21 13:10:15 +0000 I am using poky pyro (2.3) and wanted to enable aufs in linux-yocto, for genericx86, by adding KERNEL_FEATURES_append = " features/aufs/aufs-enable.scc" but unable to build the kernel and modules successfully. The error started with undefined symbol "generic_readlink" (no EXPORT_SYMBOL found) in i_op.c and incompatible pointer type in few places. As per the aufs github for the branch aufs4.10 there is no reference to generic_readlink. With this observation I am assuming that linux-yocto4.10 does not point to correct branch of aufs which is resulting in this build error. Switching to linux-yocto4.9 also giving build errors so could not able to enabled aufs. I tried the same on master branch and could not able to compile the kernel and modules successfully. Need your help in finding perfect patches. 76029 1 bruce.ashfield 2017-08-21 13:17:26 +0000 aufs is no longer carried forward by me, but is supported by the users of it in linux-yocto. I carry forward the core support, and patches are sent to deal with the changing kernel vfs layer. i.e. my last touch on it was: commit 79a6af59f8a4f06d2791f607dbfd558aaa2b1a66 Author: Bruce Ashfield <bruce.ashfield@windriver.com> Date: Tue Nov 22 11:20:29 2016 -0500 aufs: refresh for 4.9-rc6 Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> And the following fix: aufs: fix compile warning 1/1 [ Author: "Kexin(Casey) Chen" Email: Casey.Chen@windriver.com Subject: aufs: fix compile warning Date: Tue, 29 Nov 2016 14:14:07 -0800 fs/aufs/debug.h:95:19: warning: comparison of constant '0' with boolean expression is always false [-Wbool-compare] if (unlikely((e) < 0)) \ ^ fs/aufs/vdir.c:852:2: note: in expansion of macro 'AuTraceErr' AuTraceErr(!valid); ^~~~~~~~~~ In expansion of AuTraceErr(!valid), comparison of (!valid) and constant '0' always passes unlikely(x) false. function 'static int seek_vdir(struct file *file, struct dir_context *ctx)' is to find whether there is a valid vd_deblk following ctx->pos. return 1 means valid, 0 for not. Change to AuTraceErr(valid - 1) makes more sense. Signed-off-by: Kexin(Casey) Chen <Casey.Chen@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> ] ------------- I can take patches to fix the issues, but it will be several weeks since I'm currently working on 4.12 and -stable updates for all the kernels. 76157 2 bruce.ashfield 2017-08-25 14:28:13 +0000 4.10 is fixed for this now. changes will be out in a few days. onto 4.12 now. 76971 3 bruce.ashfield 2017-09-19 16:22:15 +0000 this is merged with the latest kernel SRCREVs, and is also fixed in 4.12.