mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LSM List <linux-security-module@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Smack patches for 6.1
Date: Sat, 1 Oct 2022 07:35:55 -0700	[thread overview]
Message-ID: <37208884-5153-d922-e787-e830860df05e@schaufler-ca.com> (raw)
In-Reply-To: <37208884-5153-d922-e787-e830860df05e.ref@schaufler-ca.com>

Hello Linus,

Here is the Smack pull request for v6.1.

There are two minor code clean-ups. One removes constants
left over from the old mount API. The other gets rid of an
unneeded variable. The other change fixes a flaw in handling
IPv6 labeling. All have spent time in -next and pass Smack
regression tests. Thank you.

The following changes since commit b90cb1053190353cc30f0fef0ef1f378ccc063c5:

  Linux 6.0-rc3 (2022-08-28 15:05:29 -0700)

are available in the Git repository at:

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

for you to fetch changes up to cc71271f5b793d619f8a7d2ef905374102533c75:

  smack: cleanup obsolete mount option flags (2022-09-27 10:33:03 -0700)

----------------------------------------------------------------
Smack updates for v6.1

----------------------------------------------------------------
Lontke Michael (1):
      SMACK: Add sk_clone_security LSM hook

Xiu Jianfeng (1):
      smack: cleanup obsolete mount option flags

Xu Panda (1):
      smack: lsm: remove the unneeded result variable

 security/smack/smack.h     |  9 ---------
 security/smack/smack_lsm.c | 20 +++++++++++++++++---
 2 files changed, 17 insertions(+), 12 deletions(-)


       reply	other threads:[~2022-10-01 14:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37208884-5153-d922-e787-e830860df05e.ref@schaufler-ca.com>
2022-10-01 14:35 ` Casey Schaufler [this message]
2022-10-04  1:03   ` 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=37208884-5153-d922-e787-e830860df05e@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®