From: "H. Peter Anvin" <hpa@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, x86@kernel.org
Subject: Re: linux-next: build failure in i386 since next-20100104
Date: Mon, 22 Feb 2010 18:18:59 -0800 [thread overview]
Message-ID: <4B833B13.7060109@kernel.org> (raw)
In-Reply-To: <20100222220340.4b0a19fb.sfr@canb.auug.org.au>
On 02/22/2010 03:03 AM, Stephen Rothwell wrote:
> Hi,
>
> The i386 allmodconfig builds of linux-next have been failing since
> next-20100204 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 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:212: error: call to 'copy_from_user_overflow' declared with attribute error: copy_from_user() buffer size is not provably correct
>
> [Today's linux-next is the same except for the one line starting
> "inlined" which is now:
> inlined from 'do_pages_stat' at mm/migrate.c:1012:
> ]
>
> I use gcc 4.4.3 for those compiles. (See
> http://kisskb.ellerman.id.au/kisskb/buildresult/2118967/ for full logs.)
>
> There doesn't seem to be any relevant change in the config from Feb 3 to
> 4:
>
> +CONFIG_I2C_XILINX=m
> +CONFIG_RADIO_SAA7706H=m
>
> and nothing else jumps out. The i386 defconfig and allnoconfig builds do
> not fail.
Already fixed in upstream, checkin 87b8d1adefa1548b591cbf0d63965987e2cf893d.
-hpa
next prev parent reply other threads:[~2010-02-23 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 11:03 linux-next: build failure in i386 since next-20100104 Stephen Rothwell
2010-02-23 2:18 ` H. Peter Anvin [this message]
2010-02-23 2:21 ` Stephen Rothwell
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=4B833B13.7060109@kernel.org \
--to=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@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 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.