From: Michael Schmitz <schmitzmic@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: [PATCH v5 2/2] m68k: add kernel seccomp support
Date: Sat, 26 Jun 2021 06:42:23 +1200 [thread overview]
Message-ID: <3c7cb5b1-4a31-2802-dc60-021c67aa06d3@gmail.com> (raw)
In-Reply-To: <CAMuHMdVtyTyC0L-LZPZCdNsaaxqcVLXky4dsd3m8uyyLUm9drg@mail.gmail.com>
Hi Geert,
Am 25.06.2021 um 19:31 schrieb Geert Uytterhoeven:
> Hi Michael,
>
> On Thu, Jun 24, 2021 at 11:20 PM Michael Schmitz <schmitzmic@gmail.com> wrote:
>> On 23/06/21 7:35 pm, Geert Uytterhoeven wrote:
>>> BTW, there was also "[PATCH] [WIP] selftests/seccomp: Add m68k support"
>>> https://lore.kernel.org/linux-m68k/alpine.DEB.2.21.2008261315050.25325@ramsan.of.borg/
>>>
>>> I kept on up-porting it, but haven't exercised it recently.
>>
>> See attached for test results on my ARAnyM image (Laurent's qemu image,
>> essentially).
>>
>> Is that any different from what you got in your earlier tests?
>
> Fortunately lore has a better memory than I do ;-)
>
> https://lore.kernel.org/linux-m68k/alpine.DEB.2.21.2008261612360.2926@ramsan.of.borg/
>
> mine: FAILED: 35 / 86 tests passed
> yours: FAILED: 35 / 87 tests passed
>
> So one new test, and it fails?
Looks like it. I must be missing some mail in my mail archive, can't
recall ever seeing that one.
There's one new test added after your mail was sent - KILL_unknown. I
suppose it's that one.
Anyway, both much better than without seccomp support. And going back
over the archive, I found your patch where you added seccomp.h - and
added a line in Kbuild as well, which I forgot. Will fix that.
Cheers,
Michael
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2021-06-25 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 5:39 [PATCH v5 1/2] m68k/kernel - wire up syscall_trace_enter/leave for m68k Michael Schmitz
2021-06-17 5:39 ` [PATCH v5 2/2] m68k: add kernel seccomp support Michael Schmitz
2021-06-23 7:26 ` Geert Uytterhoeven
2021-06-23 8:33 ` Michael Schmitz
2021-06-23 23:31 ` Michael Schmitz
2021-06-23 7:35 ` Geert Uytterhoeven
2021-06-24 2:12 ` Michael Schmitz
2021-06-24 2:13 ` Michael Schmitz
2021-06-24 21:20 ` Michael Schmitz
2021-06-25 7:31 ` Geert Uytterhoeven
2021-06-25 18:42 ` Michael Schmitz [this message]
2021-06-25 21:15 ` Michael Schmitz
2021-06-28 7:18 ` Geert Uytterhoeven
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=3c7cb5b1-4a31-2802-dc60-021c67aa06d3@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.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).