public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org, geert@linux-m68k.org
Cc: glaubitz@physik.fu-berlin.de, schwab@linux-m68k.org
Subject: [PATCH v7 0/2] Add kernel seccomp support for m68k
Date: Tue, 29 Jun 2021 11:55:18 +1200	[thread overview]
Message-ID: <1624924520-17567-1-git-send-email-schmitzmic@gmail.com> (raw)

Respin of m68k kernel seccomp support. 

I have added syscall_trace_enter() return code checks for
coldfire and 68000 in patch 1, and syscall_get_error(),
syscall_get_return_value() and syscall_set_arguments() defs
in patch 2 (the latter are not used without adding further
code to support tracehooks or syscall tracepoints though).


Cheers,

	Michael


             reply	other threads:[~2021-06-28 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 23:55 Michael Schmitz [this message]
2021-06-28 23:55 ` [PATCH v7 1/2] m68k/kernel - wire up syscall_trace_enter/leave for m68k Michael Schmitz
2021-06-28 23:55 ` [PATCH v7 2/2] m68k: add kernel seccomp support 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=1624924520-17567-1-git-send-email-schmitzmic@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