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
Subject: [PATCH v8 0/3] Add kernel seccomp support for m68k
Date: Thu, 13 Jan 2022 14:09:00 +1300 [thread overview]
Message-ID: <20220113010903.720-1-schmitzmic@gmail.com> (raw)
Respin of m68k kernel seccomp support, again.
I have split the (MMU) m68k switch to syscall_trace_enter()/
syscall_trace_leave() patch from the patch adding return code
checks for syscall_trace_enter() as suggested by Al Viro.
Patch 1 could now replace Eric's patch 'Stop open coding
ptrace_report_syscall'.
Rest of the series remains unchanged.
Cheers,
Michael
next reply other threads:[~2022-01-13 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 1:09 Michael Schmitz [this message]
2022-01-13 1:09 ` [PATCH v8 1/3] m68k/kernel - wire up syscall_trace_enter/leave for m68k Michael Schmitz
2022-01-13 1:09 ` [PATCH v8 2/3] m68k/kernel - check syscall_trace_enter() return code on m68k Michael Schmitz
2022-01-13 1:09 ` [PATCH v8 3/3] m68k: add kernel seccomp support Michael Schmitz
2022-01-14 22:51 ` [PATCH v8 0/3] Add kernel seccomp support for m68k John Paul Adrian Glaubitz
2022-01-17 20:49 ` Michael Schmitz
2022-01-17 18:06 ` Eric W. Biederman
2022-01-17 20:47 ` 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=20220113010903.720-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=ebiederm@xmission.com \
--cc=geert@linux-m68k.org \
--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 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).