From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Arjan van de Ven <arjan@infradead.org>,
Ritesh Raj Sarraf <rrs@researchut.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.33-rc1 build failure: copy_from_user() buffer size is not provably correct
Date: Mon, 21 Dec 2009 09:17:57 -0800 [thread overview]
Message-ID: <4B2FADC5.3020709@zytor.com> (raw)
In-Reply-To: <20091221091330.GA22867@elte.hu>
On 12/21/2009 01:13 AM, Ingo Molnar wrote:
>
> * KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
>>> from mm/migrate.c:15:
>>> In function ???copy_from_user???,
>>> inlined from ???do_pages_stat??? at mm/migrate.c:1009:
>>> /tmp/all-yes-config/2.6.33-rc1/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
>>
>> afaik, ingo already queued this fix.
>> please wait (very) few days.
>>
>> thanks.
>
> hm, the one mm/migrate.c fix we had is already in -rc1:
>
> b9255850: mm: Adjust do_pages_stat() so gcc can see copy_from_user() is safe
>
> I've Cc:-ed more folks.
>
That *is* the error report that he is describing. What version of gcc
is he using? It might be dumber than the one I have.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-12-21 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 8:34 2.6.33-rc1 build failure: copy_from_user() buffer size is not provably correct Ritesh Raj Sarraf
2009-12-21 9:07 ` KOSAKI Motohiro
2009-12-21 9:13 ` Ingo Molnar
2009-12-21 11:09 ` Ritesh Raj Sarraf
2009-12-21 17:18 ` H. Peter Anvin
2009-12-21 17:27 ` Arjan van de Ven
2009-12-21 17:17 ` H. Peter Anvin [this message]
2009-12-21 17:42 ` Ritesh Raj Sarraf
2009-12-22 0:19 ` KOSAKI Motohiro
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=4B2FADC5.3020709@zytor.com \
--to=hpa@zytor.com \
--cc=arjan@infradead.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rrs@researchut.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.