From: Andreas Schwab <schwab@linux-m68k.org>
To: Christopher Lusk <clusk@northecho.dev>
Cc: Greg Ungerer <gerg@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kees Cook <kees@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Will Drewry <wad@chromium.org>,
Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] m68k: Fix seccomp filtering on ColdFire and 68000
Date: Sun, 13 Sep 2026 12:01:03 +0200 [thread overview]
Message-ID: <87y0d5a2sg.fsf@igel.home> (raw)
In-Reply-To: <20260912230651.461269-1-clusk@northecho.dev>
On Sep 12 2026, Christopher Lusk wrote:
> diff --git a/arch/m68k/68000/entry.S b/arch/m68k/68000/entry.S
> index c257cc415..093be0a66 100644
> --- a/arch/m68k/68000/entry.S
> +++ b/arch/m68k/68000/entry.S
> @@ -81,6 +81,8 @@ ENTRY(system_call)
> getthreadinfo
> btst #(TIF_SYSCALL_TRACE%8),%a2@(TINFO_FLAGS+(31-TIF_SYSCALL_TRACE)/8)
> jne do_trace
> + btst #(TIF_SECCOMP%8),%a2@(TINFO_FLAGS+(31-TIF_SECCOMP)/8)
> + jne do_trace
Perhaps it would be faster to combine the two conditions (which jump to
the same target) with a single AND?
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2026-09-13 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 23:06 [PATCH] m68k: Fix seccomp filtering on ColdFire and 68000 Christopher Lusk
2026-09-13 10:01 ` Andreas Schwab [this message]
2026-09-13 13:17 ` [PATCH v2] " Christopher Lusk
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=87y0d5a2sg.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=clusk@northecho.dev \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=luto@kernel.org \
--cc=schmitzmic@gmail.com \
--cc=stable@vger.kernel.org \
--cc=wad@chromium.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 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.