Linux Security Modules development
 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-20260814
Date: Mon, 17 Aug 2026 19:16:40 -0400	[thread overview]
Message-ID: <4f24201cc573e07319bbc8b3e96e6abf@paul-moore.com> (raw)

Linus,

Four LSM framework patches for the Linux v7.3 merge window, the highlights
are below:

- Remove task_euid()

The task_euid(), and Rust counterpart, was never widely used, for good
reason, and now that the only user is gone we're removing it to rid
ourselves of both dead and funky code.

- Documentation improvements

Correct some of the kdoc comments for security_task_prctl() and clarify
the rust comments on task UID accessors.

- Fix a memory leak in the LSM syscall selftests

Paul

--
The following changes since commit dc59e4fea9d83f03bad6bddf3fa2e52491777482:

  Linux 7.2-rc1 (2026-06-28 12:01:31 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 0cee720cfd51402cfcb14d96cb326a36c13b823a:

  selftests/lsm: Fix memory leak in attr_lsm_count
    (2026-07-07 15:14:00 -0400)

----------------------------------------------------------------
lsm/stable-7.3 PR 20260814
----------------------------------------------------------------

Alice Ryhl (1):
      cred: delete task_euid()

Bill Roberts (1):
      lsm: clarify security_task_prctl() hook documentation

Jann Horn (1):
      rust: task: clarify comments on task UID accessors

Wang Yan (1):
      selftests/lsm: Fix memory leak in attr_lsm_count

 Documentation/security/credentials.rst                    |    6 +----
 Documentation/translations/zh_CN/security/credentials.rst |    4 ---
 include/linux/cred.h                                      |    1 
 rust/helpers/task.c                                       |    5 ----
 rust/kernel/task.rs                                       |   11 +---------
 security/security.c                                       |    5 +---
 tools/testing/selftests/lsm/common.c                      |    4 ++-
 7 files changed, 10 insertions(+), 26 deletions(-)

--
paul-moore.com

                 reply	other threads:[~2026-08-17 23:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4f24201cc573e07319bbc8b3e96e6abf@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