linux-kernel - Re: [PATCH v9 11/13] powerpc: select HAVE_SECCOMP_FILTER and provide seccomp

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]

Date:	Mon, 28 Nov 2011 11:14:41 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Will Drewry <wad@...omium.org>
Cc:	linuxppc-dev@...ts.ozlabs.org, fweisbec@...il.com,
	scarybeasts@...il.com, djm@...drot.org,
	linux-kernel@...r.kernel.org, rostedt@...dmis.org,
	segoon@...nwall.com, tglx@...utronix.de,
	Paul Mackerras <paulus@...ba.org>, kees.cook@...onical.com,
	jmorris@...ei.org, torvalds@...ux-foundation.org, mingo@...e.hu
Subject: Re: [PATCH v9 11/13] powerpc: select HAVE_SECCOMP_FILTER and
 provide seccomp_execve

On Tue, 2011-08-30 at 15:28 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2011-06-23 at 19:36 -0500, Will Drewry wrote:
> > Facilitate the use of CONFIG_SECCOMP_FILTER by wrapping compatibility
> > system call numbering for execve and selecting HAVE_SECCOMP_FILTER.
> > 
> > v9: rebase on to bccaeafd7c117acee36e90d37c7e05c19be9e7bf
> > 
> > Signed-off-by: Will Drewry <wad@...omium.org>
> 
> Seen these around for a while ... :-)
> 
> I don't see a harm in the patches per-se tho I haven't reviewed the
> actual seccomp filter stuff and it's good (or bad) behaviour on ppc.

Did that stuff every got anywhere ? I don't see HAVE_SECCOMP_FILTER
upsteam ... should I just drop the powerpc patch from patchwork ?

Cheers,
Ben.


--
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/