From: Michael Schmitz <schmitzmic@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-m68k@vger.kernel.org, geert@linux-m68k.org,
Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
Andreas Schwab <schwab@linux-m68k.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v13 0/3] Add kernel seccomp support for m68k
Date: Thu, 19 Jan 2023 11:21:30 +1300 [thread overview]
Message-ID: <2b3a641c-003f-6485-a1c1-0e0fdd45d23b@gmail.com> (raw)
In-Reply-To: <f2ce2438-8fe1-145e-64d0-9c754cee8913@physik.fu-berlin.de>
Hi Adrian,
On 18/01/23 22:43, John Paul Adrian Glaubitz wrote:
> Hi Michael!
>
> On 1/18/23 09:30, John Paul Adrian Glaubitz wrote:
>> Good catch, thank you! I added the missing definitions and it builds
>> fine now.
>>
>> Will test against a kernel with your patches now.
>
> libseccomp testsuite now fully passes on m68k, see attached.
Great - you haven't had a chance to compile the kernel selftest suite
for seccomp though?
I wonder whether some of the 'architecture difference' skipped tests are
related to the remaining seccomp_bpf self test faults??
>
> @Geert: Any chance you can approve the seccomp patches?
Now that we have m68k support for libseccomp, getting this merged is no
longer purely academic.
Both Al Viro and Andreas Schwab had provided feedback and improvements -
could you perhaps review the latest version again (v13) if that's what
is holding this up?
Cheers,
Michael
>
> Thanks,
> Adrian
>
next prev parent reply other threads:[~2023-01-18 22:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 3:55 [PATCH v13 0/3] Add kernel seccomp support for m68k Michael Schmitz
2023-01-12 3:55 ` [PATCH v13 1/3] m68k/kernel - check syscall_trace_enter() return code on m68k Michael Schmitz
2023-01-22 16:35 ` Geert Uytterhoeven
2023-01-22 16:35 ` Geert Uytterhoeven
2023-01-12 3:55 ` [PATCH v13 2/3] m68k: add kernel seccomp support Michael Schmitz
2023-01-22 16:37 ` Geert Uytterhoeven
2023-01-22 16:40 ` John Paul Adrian Glaubitz
2023-01-22 18:11 ` Michael Schmitz
2023-01-22 18:49 ` Geert Uytterhoeven
2023-01-12 3:55 ` [PATCH v13 3/3] tools/testing - seccomp test fixes for m68k Michael Schmitz
2023-01-22 16:40 ` Geert Uytterhoeven
2023-01-12 6:42 ` [PATCH v13 0/3] Add kernel seccomp support " Michael Schmitz
2023-01-13 17:29 ` John Paul Adrian Glaubitz
2023-01-14 0:00 ` Michael Schmitz
2023-01-16 9:12 ` John Paul Adrian Glaubitz
2023-01-17 2:15 ` Michael Schmitz
2023-01-17 8:08 ` John Paul Adrian Glaubitz
2023-01-17 23:25 ` Michael Schmitz
2023-01-18 8:30 ` John Paul Adrian Glaubitz
2023-01-18 9:43 ` John Paul Adrian Glaubitz
2023-01-18 22:21 ` Michael Schmitz [this message]
2023-01-19 9:18 ` John Paul Adrian Glaubitz
2023-01-20 10:45 ` John Paul Adrian Glaubitz
2023-02-27 20:45 ` Kees Cook
2023-03-07 2:57 ` Michael Schmitz
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=2b3a641c-003f-6485-a1c1-0e0fdd45d23b@gmail.com \
--to=schmitzmic@gmail.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=viro@zeniv.linux.org.uk \
/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).