Buildresult: linus/i386_defconfig/i386-gcc4.6 built on Jan 31 2019, 15:12

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	Failed
Date/Time:	Jan 31 2019, 15:12
Duration:	0:00:02.829284
Builder:	ka2
Revision:	fs/dcache: Track & report number of negative dentries (`af0c9af1b3f66052c369d08be3f60fa9a9559e48)`
Target:	linus/i386_defconfig/i386-gcc4.6
Branch:	linus
Compiler:	i386-gcc4.6 (i386-linux-gcc (GCC) 4.6.3 / GNU ld (GNU Binutils) 2.22)
Config:	i386_defconfig (download)
Log:	Download original Possible errors make[1]: * [arch/x86/Makefile:300: checkbin] Error 1 make: * [Makefile:152: sub-make] Error 2 No warnings found in log. Full Log # git rev-parse -q --verify af0c9af1b3f66052c369d08be3f60fa9a9559e48^{commit} af0c9af1b3f66052c369d08be3f60fa9a9559e48 already have revision, skipping fetch # git checkout -q -f -B kisskb af0c9af1b3f66052c369d08be3f60fa9a9559e48 # git clean -qxdf # < git log -1 # commit af0c9af1b3f66052c369d08be3f60fa9a9559e48 # Author: Waiman Long <longman@redhat.com> # Date: Wed Jan 30 13:52:38 2019 -0500 # # fs/dcache: Track & report number of negative dentries # # The current dentry number tracking code doesn't distinguish between # positive & negative dentries. It just reports the total number of # dentries in the LRU lists. # # As excessive number of negative dentries can have an impact on system # performance, it will be wise to track the number of positive and # negative dentries separately. # # This patch adds tracking for the total number of negative dentries in # the system LRU lists and reports it in the 5th field in the # /proc/sys/fs/dentry-state file. The number, however, does not include # negative dentries that are in flight but not in the LRU yet as well as # those in the shrinker lists which are on the way out anyway. # # The number of positive dentries in the LRU lists can be roughly found by # subtracting the number of negative dentries from the unused count. # # Matthew Wilcox had confirmed that since the introduction of the # dentry_stat structure in 2.1.60, the dummy array was there, probably for # future extension. They were not replacements of pre-existing fields. # So no sane applications that read the value of /proc/sys/fs/dentry-state # will do dummy thing if the last 2 fields of the sysctl parameter are not # zero. IOW, it will be safe to use one of the dummy array entry for # negative dentry count. # # Signed-off-by: Waiman Long <longman@redhat.com> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux-gcc --version # < /opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux-ld --version # < git log --format=%s --max-count=1 af0c9af1b3f66052c369d08be3f60fa9a9559e48 # < make -s -j 8 ARCH=i386 O=/kisskb/build/linus_i386_defconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- i386_defconfig # make -s -j 8 ARCH=i386 O=/kisskb/build/linus_i386_defconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- You are building kernel with non-retpoline compiler. Please update your compiler. make[1]: * [arch/x86/Makefile:300: checkbin] Error 1 make[1]: * Waiting for unfinished jobs.... make: *** [Makefile:152: sub-make] Error 2 Command 'make -s -j 8 ARCH=i386 O=/kisskb/build/linus_i386_defconfig_i386 CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/i386-linux/bin/i386-linux- ' returned non-zero exit status 2 # rm -rf /kisskb/build/linus_i386_defconfig_i386 # Build took: 0:00:02.829284

© Michael Ellerman 2006-2018.