mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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-20231030
Date: Mon, 30 Oct 2023 22:25:27 -0400	[thread overview]
Message-ID: <1cf859668ed2841067c50ebcaf01908f.paul@paul-moore.com> (raw)

Hi Linus,

Seven LSM patches for v6.7, the highlights are below:

* Add new credential functions, get_cred_many() and put_cred_many() to
  save some atomic_t operations for a few operations.  While not strictly
  LSM related, this patchset had been rotting on the mailing lists for
  some time and since the LSMs do care a lot about credentials I thought
  it reasonable to give this patch a home.

* Five patches to constify different LSM hook parameters.

* Fix a spelling mistake.

Please merge for v6.7-rc1, thanks.
-Paul

--
The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:

  Linux 6.6-rc1 (2023-09-10 16:28:41 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
    tags/lsm-pr-20231030

for you to fetch changes up to e508560672890b2873c89258b88fade1356392ce:

  lsm: fix a spelling mistake (2023-10-04 16:19:29 -0400)

----------------------------------------------------------------
lsm/stable-6.7 PR 20231030

----------------------------------------------------------------
Khadija Kamran (5):
      lsm: constify 'sb' parameter in security_quotactl()
      lsm: constify 'file' parameter in security_bprm_creds_from_file()
      lsm: constify 'bprm' parameter in security_bprm_committing_creds()
      lsm: constify 'bprm' parameter in security_bprm_committed_creds()
      lsm: constify 'sb' parameter in security_sb_kern_mount()

Mateusz Guzik (1):
      cred: add get_cred_many and put_cred_many

Paul Moore (1):
      lsm: fix a spelling mistake

 include/linux/cred.h          | 59 ++++++++++++++++++++++++++++++++-----
 include/linux/fs.h            |  2 +-
 include/linux/lsm_hook_defs.h | 10 ++++----
 include/linux/security.h      | 20 +++++++--------
 kernel/cred.c                 | 26 +++++++++++--------
 security/apparmor/lsm.c       |  4 +--
 security/commoncap.c          |  4 +--
 security/security.c           | 12 ++++-----
 security/selinux/hooks.c      | 10 ++++----
 security/tomoyo/tomoyo.c      |  2 +-
 10 files changed, 97 insertions(+), 52 deletions(-)

--
paul-moore.com

             reply	other threads:[~2023-10-31  2:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  2:25 Paul Moore [this message]
2023-10-31  6:31 ` 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=1cf859668ed2841067c50ebcaf01908f.paul@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

all inboxes | Powered by JetHome®