From: Purcareata Bogdan <b43198@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, pmoore@redhat.com,
paulus@samba.org,
Bogdan Purcareata <bogdan.purcareata@freescale.com>,
linuxppc-dev@lists.ozlabs.org, strosake@linux.vnet.ibm.com
Subject: Re: [PATCH v4 0/3] powerpc: Enable seccomp filter support
Date: Mon, 9 Mar 2015 10:26:23 +0200 [thread overview]
Message-ID: <54FD592F.7080202@freescale.com> (raw)
In-Reply-To: <1425070490.4645.86.camel@kernel.crashing.org>
On 27.02.2015 22:54, Benjamin Herrenschmidt wrote:
> On Fri, 2015-02-27 at 09:28 +0200, Purcareata Bogdan wrote:
>> Ping?
>
> What is the ping for ?
>
> Ben.
Making sure the patches are not lost on the mailing lists :) Didn't
receive any feedback on v4 and just wanted to check if there's anything
more I can do.
Thank you,
Bogdan P.
>> On 18.02.2015 10:16, Bogdan Purcareata wrote:
>>> Add the missing pieces in order to enable SECCOMP_FILTER on PowerPC
>>> architectures, and enable this support.
>>>
>>> Testing has been pursued using libseccomp with the latest ppc support patches
>>> [1][2], on Freescale platforms for both ppc and ppc64. Support on ppc64le has
>>> also been tested, courtesy of Mike Strosaker.
>>>
>>> [1] https://groups.google.com/forum/#!topic/libseccomp/oz42LfMDsxg
>>> [2] https://groups.google.com/forum/#!topic/libseccomp/TQWfCt_nD7c
>>>
>>> v4:
>>> - rebased on top of 3.19
>>>
>>> v3:
>>> - keep setting ENOSYS in syscall entry assembly when syscall tracing is disabled
>>>
>>> v2:
>>> - move setting ENOSYS from syscall entry assembly to do_syscall_trace_enter
>>>
>>> Bogdan Purcareata (3):
>>> powerpc: Don't force ENOSYS as error on syscall fail
>>> powerpc: Relax secure computing on syscall entry trace
>>> powerpc: Enable HAVE_ARCH_SECCOMP_FILTER
>>>
>>> arch/powerpc/Kconfig | 1 +
>>> arch/powerpc/kernel/entry_32.S | 7 ++++++-
>>> arch/powerpc/kernel/entry_64.S | 5 +++--
>>> arch/powerpc/kernel/ptrace.c | 8 ++++++--
>>> 4 files changed, 16 insertions(+), 5 deletions(-)
>>>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Purcareata Bogdan <b43198@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Bogdan Purcareata <bogdan.purcareata@freescale.com>,
<paulus@samba.org>, <linuxppc-dev@lists.ozlabs.org>,
<mpe@ellerman.id.au>, <linux-kernel@vger.kernel.org>,
<pmoore@redhat.com>, <strosake@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 0/3] powerpc: Enable seccomp filter support
Date: Mon, 9 Mar 2015 10:26:23 +0200 [thread overview]
Message-ID: <54FD592F.7080202@freescale.com> (raw)
In-Reply-To: <1425070490.4645.86.camel@kernel.crashing.org>
On 27.02.2015 22:54, Benjamin Herrenschmidt wrote:
> On Fri, 2015-02-27 at 09:28 +0200, Purcareata Bogdan wrote:
>> Ping?
>
> What is the ping for ?
>
> Ben.
Making sure the patches are not lost on the mailing lists :) Didn't
receive any feedback on v4 and just wanted to check if there's anything
more I can do.
Thank you,
Bogdan P.
>> On 18.02.2015 10:16, Bogdan Purcareata wrote:
>>> Add the missing pieces in order to enable SECCOMP_FILTER on PowerPC
>>> architectures, and enable this support.
>>>
>>> Testing has been pursued using libseccomp with the latest ppc support patches
>>> [1][2], on Freescale platforms for both ppc and ppc64. Support on ppc64le has
>>> also been tested, courtesy of Mike Strosaker.
>>>
>>> [1] https://groups.google.com/forum/#!topic/libseccomp/oz42LfMDsxg
>>> [2] https://groups.google.com/forum/#!topic/libseccomp/TQWfCt_nD7c
>>>
>>> v4:
>>> - rebased on top of 3.19
>>>
>>> v3:
>>> - keep setting ENOSYS in syscall entry assembly when syscall tracing is disabled
>>>
>>> v2:
>>> - move setting ENOSYS from syscall entry assembly to do_syscall_trace_enter
>>>
>>> Bogdan Purcareata (3):
>>> powerpc: Don't force ENOSYS as error on syscall fail
>>> powerpc: Relax secure computing on syscall entry trace
>>> powerpc: Enable HAVE_ARCH_SECCOMP_FILTER
>>>
>>> arch/powerpc/Kconfig | 1 +
>>> arch/powerpc/kernel/entry_32.S | 7 ++++++-
>>> arch/powerpc/kernel/entry_64.S | 5 +++--
>>> arch/powerpc/kernel/ptrace.c | 8 ++++++--
>>> 4 files changed, 16 insertions(+), 5 deletions(-)
>>>
>
>
next prev parent reply other threads:[~2015-03-09 8:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 8:16 [PATCH v4 0/3] powerpc: Enable seccomp filter support Bogdan Purcareata
2015-02-18 8:16 ` Bogdan Purcareata
2015-02-18 8:16 ` [PATCH v4 1/3] powerpc: Don't force ENOSYS as error on syscall fail Bogdan Purcareata
2015-02-18 8:16 ` Bogdan Purcareata
2015-02-18 8:16 ` [PATCH v4 2/3] powerpc: Relax secure computing on syscall entry trace Bogdan Purcareata
2015-02-18 8:16 ` Bogdan Purcareata
2015-02-18 8:16 ` [PATCH v4 3/3] powerpc: Enable HAVE_ARCH_SECCOMP_FILTER Bogdan Purcareata
2015-02-18 8:16 ` Bogdan Purcareata
2015-02-27 7:28 ` [PATCH v4 0/3] powerpc: Enable seccomp filter support Purcareata Bogdan
2015-02-27 7:28 ` Purcareata Bogdan
2015-02-27 20:54 ` Benjamin Herrenschmidt
2015-02-27 20:54 ` Benjamin Herrenschmidt
2015-03-09 8:26 ` Purcareata Bogdan [this message]
2015-03-09 8:26 ` Purcareata Bogdan
2015-03-23 11:44 ` Purcareata Bogdan
2015-03-23 11:44 ` Purcareata Bogdan
2015-03-25 9:31 ` Michael Ellerman
2015-03-25 9:31 ` Michael Ellerman
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=54FD592F.7080202@freescale.com \
--to=b43198@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=bogdan.purcareata@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=pmoore@redhat.com \
--cc=strosake@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.