From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] lsm/lsm-pr-20240131
Date: Wed, 31 Jan 2024 18:46:15 -0500 [thread overview]
Message-ID: <8b9583bc21af9323bf40a53b7f62c5c9@paul-moore.com> (raw)
Hi Linus,
Two small patches to fix some problems relating to LSM hook return values
and how the individual LSMs interact. I expect you'll probably see
another pull request similar to this in the next week (two?), to address
some remaining issues, but these two patches were ready and I wanted to
get them into your tree sooner rather than later. Please merge.
Thanks,
-Paul
--
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
tags/lsm-pr-20240131
for you to fetch changes up to 5a287d3d2b9de2b3e747132c615599907ba5c3c1:
lsm: fix default return value of the socket_getpeersec_*() hooks
(2024-01-30 17:01:54 -0500)
----------------------------------------------------------------
lsm/stable-6.8 PR 20240131
----------------------------------------------------------------
Ondrej Mosnacek (2):
lsm: fix the logic in security_inode_getsecctx()
lsm: fix default return value of the socket_getpeersec_*() hooks
include/linux/lsm_hook_defs.h | 4 ++--
security/security.c | 45 +++++++++++++++++++++++++++++++++-----
2 files changed, 42 insertions(+), 7 deletions(-)
--
paul-moore.com
next reply other threads:[~2024-01-31 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 23:46 Paul Moore [this message]
2024-02-01 18:23 ` [GIT PULL] lsm/lsm-pr-20240131 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=8b9583bc21af9323bf40a53b7f62c5c9@paul-moore.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.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