From: "Serge E. Hallyn" <serge@hallyn.com>
To: sergeh@kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Paul Moore <paul@paul-moore.com>,
Jordan Rome <linux@jordanrome.com>,
linux-security-module@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] capabilities
Date: Fri, 22 Nov 2024 11:34:18 -0600 [thread overview]
Message-ID: <20241122173418.GA518018@mail.hallyn.com> (raw)
In-Reply-To: <Zztcp-fm9Ln57c-t@lei>
On Mon, Nov 18, 2024 at 03:26:31PM +0000, sergeh@kernel.org wrote:
> Hi Linus,
Hi,
before the merge window closes, I just wanted to make sure this didn't get
lost.
thanks,
-serge
> The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
>
> Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sergeh/linux.git tags/caps-6.12-rc1
>
> for you to fetch changes up to 54eb2cec2ed7aaf25524dd5ebeaa4f87ed5c6bd6:
>
> security: add trace event for cap_capable (2024-10-30 14:40:02 -0500)
>
> This branch contains two patches:
>
> 1. Remove the cap_mmap_file() hook (Paul Moore), as it wasn't actually doing anything.
> de2433c608c2c2633b8a452dd4925d876f3d5add
>
> 2. Add a trace event for cap_capable (Jordan Rome).
> 54eb2cec2ed7aaf25524dd5ebeaa4f87ed5c6bd6
>
> Both patches have been sitting in linux-next for quite some time with no apparent
> issues.
>
> thanks,
> -serge
>
> ----------------------------------------------------------------
> 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 | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> security/commoncap.c | 37 ++++++++++++++++++++++---------------
> 3 files changed, 83 insertions(+), 15 deletions(-)
> create mode 100644 include/trace/events/capability.h
next prev parent reply other threads:[~2024-11-22 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 15:26 [GIT PULL] capabilities sergeh
2024-11-22 17:34 ` Serge E. Hallyn [this message]
2024-11-25 18:52 ` Paul Moore
2024-11-27 17:20 ` Serge E. Hallyn
2024-11-27 17:30 ` Linus Torvalds
2024-11-27 17:31 ` Linus Torvalds
2024-11-27 17:49 ` Linus Torvalds
2024-11-27 21:42 ` Serge E. Hallyn
2024-11-28 15:42 ` Jordan Rome
2024-11-28 16:28 ` Serge E. Hallyn
2024-11-28 16:35 ` Serge E. Hallyn
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=20241122173418.GA518018@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@jordanrome.com \
--cc=paul@paul-moore.com \
--cc=sergeh@kernel.org \
--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).