From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Ayushman Dutta <ayudutta@amazon.com>,
Christian Brauner <brauner@kernel.org>,
Gautam Menghani <gautammenghani201@gmail.com>,
Kees Cook <keescook@chromium.org>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Randy Dunlap <rdunlap@infradead.org>,
syzbot+ab17848fe269b573eb71@syzkaller.appspotmail.com
Subject: [GIT PULL] seccomp updates for v6.2-rc1
Date: Mon, 5 Dec 2022 16:30:24 -0800 [thread overview]
Message-ID: <202212051629.61BD1239E@keescook> (raw)
Hi Linus,
Please pull these 3 seccomp updates for v6.2-rc1.
Thanks!
-Kees
The following changes since commit 247f34f7b80357943234f93f247a1ae6b6c3a740:
Linux 6.1-rc2 (2022-10-23 15:27:33 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v6.2-rc1
for you to fetch changes up to b9069728a70c23dad00684eb994a3f5295f127cf:
seccomp: document the "filter_count" field (2022-12-02 11:33:48 -0800)
----------------------------------------------------------------
seccomp updates for v6.2-rc1
- Add missing kerndoc parameter (Randy Dunlap).
- Improve seccomp selftest to check CAP_SYS_ADMIN (Gautam Menghani).
- Fix allocation leak when cloned thread immediately dies (Kuniyuki Iwashima).
----------------------------------------------------------------
Gautam Menghani (1):
selftests/seccomp: Check CAP_SYS_ADMIN capability in the test mode_filter_without_nnp
Kuniyuki Iwashima (1):
seccomp: Move copy_seccomp() to no failure path.
Randy Dunlap (1):
seccomp: document the "filter_count" field
include/linux/seccomp.h | 1 +
kernel/fork.c | 17 +++++++++++------
tools/testing/selftests/seccomp/seccomp_bpf.c | 6 ++++--
3 files changed, 16 insertions(+), 8 deletions(-)
--
Kees Cook
next reply other threads:[~2022-12-06 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 0:30 Kees Cook [this message]
2022-12-12 17:33 ` [GIT PULL] seccomp updates for v6.2-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=202212051629.61BD1239E@keescook \
--to=keescook@chromium.org \
--cc=ayudutta@amazon.com \
--cc=brauner@kernel.org \
--cc=gautammenghani201@gmail.com \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=syzbot+ab17848fe269b573eb71@syzkaller.appspotmail.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).