mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: torvalds@linux-foundation.org
Cc: LSM List <linux-security-module@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	casey@schaufler-ca.com
Subject: [GIT PULL] Smack patches for v6.0
Date: Mon, 1 Aug 2022 13:13:20 -0700	[thread overview]
Message-ID: <827a0fe0-03a3-b5ca-db34-daff17095b8f@schaufler-ca.com> (raw)
In-Reply-To: <827a0fe0-03a3-b5ca-db34-daff17095b8f.ref@schaufler-ca.com>

Hello Linus,

Here is the Smack pull request for v6.0.

There are two minor code clean-ups. One removes a touch of
dead code and the other replaces an instance of kzalloc + strncpy
with kstrndup. The changes have been in next and pass all tests.
Thank you.

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

  https://github.com/cschaufler/smack-next tags/Smack-for-6.0

for you to fetch changes up to aa16fb4b9e7e1057008d999138e7ae68a40bf167:

  smack: Remove the redundant lsm_inode_alloc (2022-08-01 11:26:09 -0700)

----------------------------------------------------------------
Two minor code clean-ups for Smack.

----------------------------------------------------------------
GONG, Ruiqi (1):
      smack: Replace kzalloc + strncpy with kstrndup

Xiu Jianfeng (1):
      smack: Remove the redundant lsm_inode_alloc

 security/smack/smack_access.c | 7 ++-----
 security/smack/smack_lsm.c    | 7 -------
 2 files changed, 2 insertions(+), 12 deletions(-)


       reply	other threads:[~2022-08-01 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <827a0fe0-03a3-b5ca-db34-daff17095b8f.ref@schaufler-ca.com>
2022-08-01 20:13 ` Casey Schaufler [this message]
2022-08-02 22:11   ` Linus Torvalds
2022-08-02 22:29   ` 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=827a0fe0-03a3-b5ca-db34-daff17095b8f@schaufler-ca.com \
    --to=casey@schaufler-ca.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®