mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 28 ("copy_from_user_overflow" undefined)
Date: Thu, 28 Jul 2011 16:01:36 -0700	[thread overview]
Message-ID: <20110728160136.771e2c0a.rdunlap@xenotime.net> (raw)
In-Reply-To: <CA+icZUV7R5hqTupiuZZKWcsZ5LOBGmY6xgmMTM7W3ojJo0Sp4w@mail.gmail.com>

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 ***

  reply	other threads:[~2011-07-28 23:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 14:05 linux-next: Tree for July 28 (fs/binfmt_misc.ko) Sedat Dilek
2011-07-28 23:01 ` Randy Dunlap [this message]
2011-07-29  1:34   ` linux-next: Tree for July 28 ("copy_from_user_overflow" undefined) Sedat Dilek
2011-07-29  5:09     ` Randy Dunlap
2011-07-29  9:02       ` Sedat Dilek
2011-07-29  9:45         ` Sedat Dilek
2011-07-29 11:07           ` Sedat Dilek
2011-07-29 15:13             ` Randy Dunlap
2011-07-29 15:33               ` Sedat Dilek
2011-07-29 17:50           ` Stephen Boyd
2011-07-29 18:09             ` Sedat Dilek
2011-07-29 18:21             ` Randy Dunlap
2011-07-29 18:59               ` Sedat Dilek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110728160136.771e2c0a.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®