The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <kees@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Mateusz Guzik <mjguzik@gmail.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: [GIT PULL] seccomp updates for v6.15-rc1
Date: Mon, 17 Mar 2025 09:09:34 -0700	[thread overview]
Message-ID: <202503170909.7FBAC1E@keescook> (raw)

Hi Linus,

Please pull these seccomp updates for v6.15-rc1.

Thanks!

-Kees

The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:

  Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.15-rc1

for you to fetch changes up to 8f19331384e6ca816f5bea20ab45c4b72a5cd05f:

  seccomp: avoid the lock trip seccomp_filter_release in common case (2025-02-24 11:17:10 -0800)

----------------------------------------------------------------
seccomp updates for v6.15-rc1

- avoid the lock trip seccomp_filter_release in common case (Mateusz Guzik)

- remove unused 'sd' argument through-out (Oleg Nesterov)

- selftests/seccomp: Add hard-coded __NR_uretprobe for x86_64

----------------------------------------------------------------
Kees Cook (1):
      selftests/seccomp: Add hard-coded __NR_uretprobe for x86_64

Mateusz Guzik (1):
      seccomp: avoid the lock trip seccomp_filter_release in common case

Oleg Nesterov (4):
      seccomp/mips: change syscall_trace_enter() to use secure_computing()
      seccomp: fix the __secure_computing() stub for !HAVE_ARCH_SECCOMP_FILTER
      seccomp: remove the 'sd' argument from __secure_computing()
      seccomp: remove the 'sd' argument from __seccomp_filter()

 arch/mips/kernel/ptrace.c                     | 20 ++---------
 arch/powerpc/kernel/ptrace/ptrace.c           |  2 +-
 include/linux/seccomp.h                       | 12 +++----
 kernel/entry/common.c                         |  2 +-
 kernel/seccomp.c                              | 49 ++++++++++++++++-----------
 tools/testing/selftests/seccomp/seccomp_bpf.c |  6 ++++
 6 files changed, 43 insertions(+), 48 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2025-03-17 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 16:09 Kees Cook [this message]
2025-03-25  0:45 ` [GIT PULL] seccomp updates for v6.15-rc1 pr-tracker-bot

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=202503170909.7FBAC1E@keescook \
    --to=kees@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=oleg@redhat.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tsbogend@alpha.franken.de \
    /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