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.6
Date: Tue, 29 Aug 2023 16:44:24 -0700 [thread overview]
Message-ID: <d8c21494-583f-8da2-a2cb-cd5410a13900@schaufler-ca.com> (raw)
In-Reply-To: <d8c21494-583f-8da2-a2cb-cd5410a13900.ref@schaufler-ca.com>
Hello Linus,
Here is the Smack pull request for v6.6.
There are two patches. One is a simple spelling fix. The other is a
bounds check for a very likely underflow. These updates have been in
the next branch and pass all tests. Thank you.
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
are available in the Git repository at:
https://github.com/cschaufler/smack-next tags/Smack-for-6.6
for you to fetch changes up to 3ad49d37cf5759c3b8b68d02e3563f633d9c1aee:
smackfs: Prevent underflow in smk_set_cipso() (2023-08-07 14:09:23 -0700)
----------------------------------------------------------------
Smack updates for v6.6. Two minor fixes.
----------------------------------------------------------------
Dan Carpenter (1):
smackfs: Prevent underflow in smk_set_cipso()
Tóth János (1):
security: smack: smackfs: fix typo (lables->labels)
security/smack/smackfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
next parent reply other threads:[~2023-08-29 23:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d8c21494-583f-8da2-a2cb-cd5410a13900.ref@schaufler-ca.com>
2023-08-29 23:44 ` Casey Schaufler [this message]
2023-08-30 16:34 ` 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=d8c21494-583f-8da2-a2cb-cd5410a13900@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®