From: Boaz Harrosh <bharrosh@panasas.com>
To: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: build error with DEBUG_STRICT_USER_COPY_CHECKS on at mm/migrate.c:1009
Date: Wed, 30 Dec 2009 19:35:22 +0200 [thread overview]
Message-ID: <4B3B8F5A.9050601@panasas.com> (raw)
Arjan hi
building with ARCH=i386 allmodconfig will give me the below compilation error.
I'm on FC12 [gcc (GCC) 4.4.2 20091222 (Red Hat 4.4.2-20)]
In file included from arch/x86/include/asm/uaccess.h:571,
from include/linux/uaccess.h:5,
from include/linux/highmem.h:6,
from include/linux/pagemap.h:10,
from include/linux/mempolicy.h:62,
from include/linux/migrate.h:5,
from mm/migrate.c:15:
In function 'copy_from_user',
inlined from 'do_pages_stat' at mm/migrate.c:1009:
arch/x86/include/asm/uaccess_32.h:213: error: call to 'copy_from_user_overflow' declared with attribute error: copy_from_user() buffer size is not provably correct
un-setting DEBUG_STRICT_USER_COPY_CHECKS, (It was turned on by allmodconfig) will let
the kernel compile.
I thought you might want to know
Boaz
reply other threads:[~2009-12-30 17:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B3B8F5A.9050601@panasas.com \
--to=bharrosh@panasas.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
/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