From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: ebiederm@xmission.com, viro@zeniv.linux.org.uk,
glaubitz@physik.fu-berlin.de
Subject: [PATCH v10 0/3] Add kernel seccomp support for m68k
Date: Thu, 27 Jan 2022 20:41:55 +1300 [thread overview]
Message-ID: <20220127074158.25888-1-schmitzmic@gmail.com> (raw)
Patch 3 adds the test for TIF_SECCOMP thread info flag to call
into syscall_trace_enter() when seccomp syscall filtering
is active, which was missing from earlier versions (classic
MMU m68k only - need some help with the test for 68000 and
coldfire).
The previous version required the TIF_SYSCALL_TRACE
flag to be set for syscall filtering to work
The rest of the series remains unchanged from v9.
Tested on ARAnyM, 63 out of 89 seccomp_bpf tests now pass
(33 with the old version).
I hope you didn't waste too much effort on testing v8/v9, Adrian.
Should have a suitably large brown paper bag somewhere yet :-(
Cheers,
Michael
next reply other threads:[~2022-01-27 7:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 7:41 Michael Schmitz [this message]
2022-01-27 7:41 ` [PATCH v10 1/3] m68k/kernel - wire up syscall_trace_enter/leave for m68k Michael Schmitz
2022-05-09 11:06 ` Geert Uytterhoeven
2022-01-27 7:41 ` [PATCH v10 2/3] m68k/kernel - check syscall_trace_enter() return code on m68k Michael Schmitz
2022-01-27 7:41 ` [PATCH v10 3/3] m68k: add kernel seccomp support Michael Schmitz
2022-01-27 9:09 ` [PATCH v10 0/3] Add kernel seccomp support for m68k John Paul Adrian Glaubitz
2022-01-28 6:51 ` Michael Schmitz
2022-05-03 21:53 ` Eric W. Biederman
2022-05-06 8:37 ` Michael Schmitz
2022-05-09 11:16 ` 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=20220127074158.25888-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.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 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.