linux-kernel - Re: linux-next: build warning after merge of the final tree (security tree related)

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] [day] [month] [year] [list]

Date:	Tue, 17 Apr 2012 11:06:48 -0500
From:	Will Drewry <wad@...omium.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	James Morris <jmorris@...ei.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, Kees Cook <keescook@...omium.org>,
	Eric Paris <eparis@...hat.com>,
	Serge Hallyn <serge.hallyn@...onical.com>
Subject: Re: linux-next: build warning after merge of the final tree (security
 tree related)

Doh - thanks! I'll figure out the right way to silence these warnings
in this config case and post the patch against James's tree.

Thanks!

On Mon, Apr 16, 2012 at 11:10 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (sparc64 defconfig)
> produced this warning:
>
> kernel/seccomp.c: In function '__secure_computing':
> kernel/seccomp.c:445:1: warning: label 'skip' defined but not used [-Wunused-label]
> kernel/seccomp.c:381:6: warning: unused variable 'data' [-Wunused-variable]
> kernel/seccomp.c:380:6: warning: unused variable 'ret' [-Wunused-variable]
>
> Introduced by commit acf3b2c71ed2 ("seccomp: add SECCOMP_RET_ERRNO").
> This build has CONFIG_SECCOMP_FILTER turned off.
>
> --
> Cheers,
> Stephen Rothwell                    sfr@...b.auug.org.au
--
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/