From: "Serge E. Hallyn" <serge@hallyn.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Paul Moore <paul@paul-moore.com>,
Jordan Rome <linux@jordanrome.com>,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] capabilities changes for 6.14-rc1
Date: Mon, 20 Jan 2025 15:59:44 -0600 [thread overview]
Message-ID: <20250120215944.GA16878@mail.hallyn.com> (raw)
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git tags/caps-6.13-rc1
for you to fetch changes up to d48da4d5ed7b4a022a4e54f210575baac71f58af:
security: add trace event for cap_capable (2024-12-04 20:59:21 -0600)
----------------------------------------------------------------
capabilities patches for 6.14-rc1
This branch contains basically the same two patches as last time:
1. A patch by Paul Moore to remove the cap_mmap_file() hook, as it simply
returned the default return value and so doesn't need to exist.
2. A patch by Jordan Rome to add a trace event for cap_capable(), updated
to address your feedback during the last cycle.
Both patches have been sitting in linux-next since 6.13-rc1 with no
issues.
Signed-off-by: Serge E. Hallyn <serge@hallyn.com>
----------------------------------------------------------------
Jordan Rome (1):
security: add trace event for cap_capable
Paul Moore (1):
capabilities: remove cap_mmap_file()
MAINTAINERS | 1 +
include/trace/events/capability.h | 57 ++++++++++++++++++++++++++++++++++++
security/commoncap.c | 61 ++++++++++++++++++++++++++-------------
3 files changed, 99 insertions(+), 20 deletions(-)
create mode 100644 include/trace/events/capability.h
next reply other threads:[~2025-01-20 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 21:59 Serge E. Hallyn [this message]
2025-01-23 16:21 ` [GIT PULL] capabilities changes for 6.14-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=20250120215944.GA16878@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@jordanrome.com \
--cc=paul@paul-moore.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).