On Fri, 29 Jul 2011 03:34:26 +0200 Sedat Dilek wrote: > On Fri, Jul 29, 2011 at 1:01 AM, Randy Dunlap <rdunlap@xxxxxxxxxxxx> wrote: > > On Thu, 28 Jul 2011 16:05:31 +0200 Sedat Dilek wrote: > > > >> Hi, > >> > >> just see this build-break on the last mile: > >> > >> [...] > >> OBJCOPY arch/x86/boot/compressed/vmlinux.bin > >> HOSTCC arch/x86/boot/compressed/relocs > >> HOSTCC arch/x86/boot/compressed/mkpiggy > >> /mnt/sdb3/linux-kernel/linux-3.0/debian/build/source_i386_none/arch/x86/boot/compressed/relocs.c: > >> In function 'print_absolute_symbols': > >> /mnt/sdb3/linux-kernel/linux-3.0/debian/build/source_i386_none/arch/x86/boot/compressed/relocs.c:405:14: > >> warning: variable 'sh_symtab' set but not used > >> [-Wunused-but-set-variable] > >> ERROR: "copy_from_user_overflow" [fs/binfmt_misc.ko] undefined! > >> make[5]: *** [__modpost] Error 1 > >> make[4]: *** [modules] Error 2 > >> make[4]: *** Waiting for unfinished jobs.... > >> RELOCS arch/x86/boot/compressed/vmlinux.relocs > >> GZIP arch/x86/boot/compressed/vmlinux.bin.gz > >> MKPIGGY arch/x86/boot/compressed/piggy.S > >> AS arch/x86/boot/compressed/piggy.o > >> LD arch/x86/boot/compressed/vmlinux > >> ZOFFSET arch/x86/boot/zoffset.h > >> OBJCOPY arch/x86/boot/vmlinux.bin > >> AS arch/x86/boot/header.o > >> LD arch/x86/boot/setup.elf > >> OBJCOPY arch/x86/boot/setup.bin > >> BUILD arch/x86/boot/bzImage > >> Setup is 15596 bytes (padded to 15872 bytes). > >> System is 2471 kB > >> CRC eb598167 > >> Kernel: arch/x86/boot/bzImage is ready (#1) > >> make[3]: *** [sub-make] Error 2 > >> make[2]: *** [all] Error 2 > >> > >> I have these binfmt kernel-config options set: > >> > >> CONFIG_BINFMT_ELF=y > >> # CONFIG_BINFMT_AOUT is not set > >> CONFIG_BINFMT_MISC=m > > > > How does someone turn off this error message? > > > > I have: > > # CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is not set > > # CONFIG_STRICT_DEVMEM is not set > > > > and I still cannot get this error to go away (on x86_64). > > > > > > --- > > ~Randy > > *** Remember to use Documentation/SubmitChecklist when testing your code *** > > > > Can you say with which linux-next version you saw this first? > My last version was next-20110722 (which was OK). It looks like 2011-0727 has lots of these errors in my randconfig builds, but I can't say that they are all incorrect, so it's not very conclusive. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
