From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: sparc tree build warning
Date: Thu, 28 Jan 2010 20:12:06 -0800 (PST) [thread overview]
Message-ID: <20100128.201206.257650090.davem@davemloft.net> (raw)
In-Reply-To: <20100129102543.7af32673.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 29 Jan 2010 10:25:43 +1100
> Hi Dave,
>
> On Thu, 28 Jan 2010 05:24:32 -0800 (PST) David Miller <davem@davemloft.net> wrote:
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Thu, 28 Jan 2010 18:44:23 +1100
>>
>> > I am still seeing these. Is it my compiler version (gcc4.4.0)?
>>
>> You can't turn on DEBUG_STRICT_USER_COPY_CHECKS and
>> expect a successful build. It's for developers to
>> look at the errors that are generated and audit those
>> cases in detail.
>
> These are defconfig builds and CONFIG_DEBUG_STRICT_USER_COPY_CHECKS is
> not set in either case.
Simply ignore the warning then, I thought you were reporting
a build failure.
> I only do an i386 defconfig build and I don't get these warnings.
Looking at the specific case of net/core/pktgen.c:867
"len" is variable in the net/core/pktgen.c line that emits the
warning
Even though it is limited to "sizeof(name) - 1" via strn_len()'s
third argument, that's a lot to expect the compiler to dig into
and be able to conclude invariants from.
Please just ignore the warnings.
Thanks.
next prev parent reply other threads:[~2010-01-29 4:11 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
2010-01-28 13:24 ` David Miller
2010-01-28 23:25 ` Stephen Rothwell
2010-01-29 4:12 ` David Miller [this message]
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=20100128.201206.257650090.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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