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>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: [GIT PULL] Smack patches for 6.5
Date: Tue, 27 Jun 2023 08:01:44 -0700 [thread overview]
Message-ID: <3b1107c2-77c1-28ce-3413-bec589eae083@schaufler-ca.com> (raw)
In-Reply-To: <3b1107c2-77c1-28ce-3413-bec589eae083.ref@schaufler-ca.com>
Hello Linus,
Here is the Smack pull request for v6.5.
There are two patches, both of which change how Smack initializes
the SMACK64TRANSMUTE extended attribute. The first corrects the
behavior of overlayfs, which creates inodes differently from other
filesystems. The second ensures that transmute attributes specified
by mount options are correctly assigned. These updates have been in
the next branch and pass all tests. Thank you.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
https://github.com/cschaufler/smack-next tags/Smack-for-6.5
for you to fetch changes up to 2c085f3a8f23c9b444e8b99d93c15d7ce870fc4e:
smack: Record transmuting in smk_transmuted (2023-05-11 10:05:39 -0700)
----------------------------------------------------------------
Two patches that improve inode attribute initialization.
----------------------------------------------------------------
Roberto Sassu (2):
smack: Retrieve transmuting information in smack_inode_getsecurity()
smack: Record transmuting in smk_transmuted
security/smack/smack.h | 1 +
security/smack/smack_lsm.c | 63 ++++++++++++++++++++++++++++++++++------------
2 files changed, 48 insertions(+), 16 deletions(-)
next parent reply other threads:[~2023-06-27 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3b1107c2-77c1-28ce-3413-bec589eae083.ref@schaufler-ca.com>
2023-06-27 15:01 ` Casey Schaufler [this message]
2023-06-28 1:01 ` 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=3b1107c2-77c1-28ce-3413-bec589eae083@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®