linux-kernel - Re: linux-next: sparc tree build warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100128.201206.257650090.davem@davemloft.net>
Date:	Thu, 28 Jan 2010 20:12:06 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	sfr@...b.auug.org.au
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: sparc tree build warning

From: Stephen Rothwell <sfr@...b.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@...emloft.net> wrote:
>>
>> From: Stephen Rothwell <sfr@...b.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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/