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>,
XU pengfei <xupengfei@nfschina.com>
Subject: [GIT PULL] Smack patches for v6.4
Date: Mon, 24 Apr 2023 11:01:40 -0700 [thread overview]
Message-ID: <d4160d44-6dd4-abdf-e125-e3f5673445c9@schaufler-ca.com> (raw)
In-Reply-To: <d4160d44-6dd4-abdf-e125-e3f5673445c9.ref@schaufler-ca.com>
Hello Linus,
Here is the Smack pull request for v6.4.
There are two changes. One is the removal of an unnecessary cast.
The other is more substantial. The mount option processing introduced
with the mount rework makes copies of mount option values. There is
no good reason to make copies of Smack labels, as they are maintained
on a list and never removed. The code now uses pointers to entries
on the list, reducing processing time and memory use. These changes
have been in the next branch and pass all tests. Thank you.
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
https://github.com/cschaufler/smack-next tags/Smack-for-6.4
for you to fetch changes up to de93e515db306767549bb29a926f523ca2a601ab:
Smack: Improve mount process memory use (2023-04-05 08:46:14 -0700)
----------------------------------------------------------------
Smack updates for v6.4
----------------------------------------------------------------
Casey Schaufler (1):
Smack: Improve mount process memory use
XU pengfei (1):
smack_lsm: remove unnecessary type casting
security/smack/smack_lsm.c | 64 +++++++++++++++++-----------------------------
1 file changed, 24 insertions(+), 40 deletions(-)
next parent reply other threads:[~2023-04-24 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4160d44-6dd4-abdf-e125-e3f5673445c9.ref@schaufler-ca.com>
2023-04-24 18:01 ` Casey Schaufler [this message]
2023-04-24 18:47 ` 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=d4160d44-6dd4-abdf-e125-e3f5673445c9@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 \
--cc=xupengfei@nfschina.com \
/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®