From: Will Drewry <wad@chromium.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: fweisbec@gmail.com, scarybeasts@gmail.com, djm@mindrot.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
jmorris@namei.org, torvalds@linux-foundation.org,
kees.cook@canonical.com, Paul Mackerras <paulus@samba.org>,
mingo@elte.hu, tglx@linutronix.de, linuxppc-dev@lists.ozlabs.org,
segoon@openwall.com
Subject: Re: [PATCH v9 11/13] powerpc: select HAVE_SECCOMP_FILTER and provide seccomp_execve
Date: Sun, 27 Nov 2011 19:45:45 -0600 [thread overview]
Message-ID: <CABqD9haiwc4zretJS2haYmGA0pY9vd1CSOAdhE_HsA7g7RaxSQ@mail.gmail.com> (raw)
In-Reply-To: <1322439281.23348.34.camel@pasglop>
On Sun, Nov 27, 2011 at 6:14 PM, Benjamin Herrenschmidt
<benh@kernel.crashing.org> wrote:
> 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@chromium.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 ?
Thanks for following up! At present, it stalled out, so I think it'd
make sense to just drop it. I will repost the series soon-ish and see
if any progress can be made. [I've explored a number of alternative
approaches and still think something along the seccomp_filter lines is
still rational.]
cheers!
will
prev parent reply other threads:[~2011-11-28 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308875813-20122-1-git-send-email-wad@chromium.org>
2011-06-24 0:36 ` [PATCH v9 11/13] powerpc: select HAVE_SECCOMP_FILTER and provide seccomp_execve Will Drewry
2011-08-30 5:28 ` Benjamin Herrenschmidt
2011-11-28 0:14 ` Benjamin Herrenschmidt
2011-11-28 1:45 ` Will Drewry [this message]
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=CABqD9haiwc4zretJS2haYmGA0pY9vd1CSOAdhE_HsA7g7RaxSQ@mail.gmail.com \
--to=wad@chromium.org \
--cc=benh@kernel.crashing.org \
--cc=djm@mindrot.org \
--cc=fweisbec@gmail.com \
--cc=jmorris@namei.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=scarybeasts@gmail.com \
--cc=segoon@openwall.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).