From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Wessel <jason.wessel@windriver•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Frederic Weisbecker <fweisbec@gmail•com>,
Steven Rostedt <rostedt@goodmis•org>
Subject: linux-next: build failure after merge of the final tree (kgdb tree related)
Date: Wed, 28 Jul 2010 14:05:56 +1000 [thread overview]
Message-ID: <20100728140556.2bdacbf3.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Hi all,
After merging the final tree, next-20100726 build (i386 allmodconfig)
failed like this:
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 kernel/trace/trace.c:24:
arch/x86/include/asm/uaccess_32.h: In function 'copy_from_user':
arch/x86/include/asm/uaccess_32.h:212: error: call to 'copy_from_user_overflow' declared with attribute error: copy_from_user() buffer size is not provably correct
Probably caused by commit e5738a3d75254c6d135ccad925e513ddb860967e
("ftrace,kdb: Extend kdb to be able to dump the ftrace buffer") from the
kgdb tree which turned off optimization (and therefore probably inlining)
for kernel/trace/trace.c ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-07-28 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 4:05 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-01 4:22 linux-next: build failure after merge of the final tree (kgdb tree related) Stephen Rothwell
2011-08-01 12:42 ` Jason Wessel
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=20100728140556.2bdacbf3.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=fweisbec@gmail$(echo .)com \
--cc=jason.wessel@windriver$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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