From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "David S. Miller" <davem@davemloft•net>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: sparc tree build warning
Date: Thu, 28 Jan 2010 18:44:23 +1100 [thread overview]
Message-ID: <20100128184423.40ce38fb.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20091214163338.f811722f.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
Hi Dave,
On Mon, 14 Dec 2009 16:33:38 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next build (sparc defconfig) produced this warning:
>
> In file included from arch/sparc/include/asm/uaccess.h:7,
> from include/net/checksum.h:26,
> from include/linux/skbuff.h:29,
> from net/core/pktgen.c:141:
> In function 'copy_from_user',
> inlined from 'pktgen_if_write' at net/core/pktgen.c:867:
> arch/sparc/include/asm/uaccess_32.h:276: warning: call to 'copy_from_user_overflow' declared with attribute warning: copy_from_user() buffer size is not provably correct
>
> and many more.
>
> The sparc64 defconfig build produced many similar warnings:
>
> In file included from arch/sparc/include/asm/uaccess.h:5,
> from include/linux/uaccess.h:6,
> from include/linux/highmem.h:7,
> from include/linux/pagemap.h:11,
> from include/linux/mempolicy.h:63,
> from mm/mempolicy.c:69:
> arch/sparc/include/asm/uaccess_64.h: In function 'compat_sys_get_mempolicy':
> arch/sparc/include/asm/uaccess_64.h:232: warning: call to 'copy_from_user_overflow' declared with attribute warning: copy_from_user() buffer size is not provably correct
I am still seeing these. Is it my compiler version (gcc4.4.0)?
--
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 prev parent reply other threads:[~2010-01-28 7:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 5:33 linux-next: sparc tree build warning Stephen Rothwell
2009-12-14 7:01 ` David Miller
2009-12-14 8:55 ` Stephen Rothwell
2009-12-14 7:40 ` David Miller
2009-12-14 9:00 ` Stephen Rothwell
2010-01-28 7:44 ` Stephen Rothwell [this message]
2010-01-28 13:24 ` David Miller
2010-01-28 23:25 ` Stephen Rothwell
2010-01-29 4:12 ` David Miller
2010-01-29 6:32 ` 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=20100128184423.40ce38fb.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=davem@davemloft$(echo .)net \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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