From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Wim Van Sebroeck <wim@iguana.be>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: linux-next: build warnings (buffer size is not provably correct)
Date: Thu, 8 Oct 2009 15:47:10 +1100 [thread overview]
Message-ID: <20091008154710.a351a56b.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
Hi all,
Today's linux-next build (i386 defconfig) produced these warnings:
In file included from arch/x86/include/asm/uaccess.h:572,
from kernel/capability.c:18:
arch/x86/include/asm/uaccess_32.h: In function 'sys_capset':
arch/x86/include/asm/uaccess_32.h:211: warning: call to 'copy_from_user_overflow' declared with attribute warning: copy_from_user() buffer size is not provably correct
In file included from arch/x86/include/asm/uaccess.h:572,
from include/linux/poll.h:14,
from include/linux/rtc.h:115,
from include/linux/mc146818rtc.h:16,
from drivers/char/nvram.c:108:
arch/x86/include/asm/uaccess_32.h: In function 'nvram_write':
arch/x86/include/asm/uaccess_32.h:211: warning: call to 'copy_from_user_overflow' declared with attribute warning: copy_from_user() buffer size is not provably correct
Brought to light by commit 4a3127693001c61a21d1ce680db6340623f52e93
("x86: Turn the copy_from_user check into an (optional) compile time
warning") from the tip tree.
Clearly these are not problems with the tip tree, but someone may want to
look at them.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-10-08 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 4:47 Stephen Rothwell [this message]
2009-10-08 13:42 ` Arjan van de Ven
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=20091008154710.a351a56b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=wim@iguana.be \
/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®