Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABqD9hZe9t9WeMRcuhvevSb9svp5UH9ZHH4TZg753zzcrX-tnQ@mail.gmail.com>
Date: Mon, 26 Mar 2012 11:53:06 -0500
From: Will Drewry <wad@...omium.org>
To: "H. Peter Anvin" <hpa@...or.com>, akpm@...ux-foundation.org
Cc: linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org, 
	linux-doc@...r.kernel.org, kernel-hardening@...ts.openwall.com, 
	netdev@...r.kernel.org, x86@...nel.org, arnd@...db.de, davem@...emloft.net, 
	mingo@...hat.com, oleg@...hat.com, peterz@...radead.org, rdunlap@...otime.net, 
	mcgrathr@...omium.org, tglx@...utronix.de, luto@....edu, eparis@...hat.com, 
	serge.hallyn@...onical.com, djm@...drot.org, scarybeasts@...il.com, 
	indan@....nu, pmoore@...hat.com, corbet@....net, eric.dumazet@...il.com, 
	markus@...omium.org, coreyb@...ux.vnet.ibm.com, keescook@...omium.org
Subject: Re: [PATCH v15 00/13] seccomp_filter: syscall filtering using BPF

On Sun, Mar 25, 2012 at 2:36 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 03/14/2012 08:11 PM, Will Drewry wrote:
>> Please see prior revisions of this patch series for a high
>> level blurb.
>>
>> This revision makes a number of refinements and tweaks. The biggest
>> change is a slight renumbering of the return codes which will break
>> existing code using this patch series.
>>
>> I believe this patch is in good shape, and I don't see the need for
>> any more API changes at this point.  I plan to start using this revision
>> more extensively, and I'd certainly appreciate any testing.
>>
>> Thanks!
>> will
>>
>
> x86 portions:
>
> Reviewed-by: H. Peter Anvin <hpa@...or.com>

Thanks!

> What is the preferred way to push this upstream?  (Presumably for 3.5 at
> this point, but we should get it into -next as soon as possible after
> the merge window.)

A repost when rc1 has been cut is what's been suggested to me.

Additionally, two tweaks have been pointed out off list (documentation
cruft and lack if #ifdef for asm/syscall.h), which I have fixed in my
local and github tree but haven't yet reposted here.  I was planning
on just posting v17 when rc1 is cut (unless I've blithely missed it
already) and then trying to pester everyone and anyone who can merge.
:)

Maybe someone more authoritative than me will answer though.

thanks!
will

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.