From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Security Module list
<linux-security-module@vger.kernel.org>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: [GIT PULL] Smack patches for v5.12
Date: Tue, 16 Feb 2021 14:06:51 -0800 [thread overview]
Message-ID: <7fc1be79-b611-24e9-f2fb-282dd061d755@schaufler-ca.com> (raw)
In-Reply-To: 7fc1be79-b611-24e9-f2fb-282dd061d755.ref@schaufler-ca.com
Hello Linus
Here is a Smack change for the 5.12 release. It introduces bound checking
for the smackfs administrative interfaces where they were missing.
--
The following changes since commit 1048ba83fb1c00cd24172e23e8263972f6b5d9ac:
Linux 5.11-rc6 (2021-01-31 13:50:09 -0800)
are available in the Git repository at:
https://github.com/cschaufler/smack-next tags/Smack-for-v5.12
for you to fetch changes up to 7ef4c19d245f3dc233fd4be5acea436edd1d83d8:
smackfs: restrict bytes count in smackfs write functions (2021-02-02 17:14:02 -0800)
----------------------------------------------------------------
Smack updates for v5.12.
Bounds checking for writes to smackfs interfaces.
----------------------------------------------------------------
Sabyrzhan Tasbolatov (1):
smackfs: restrict bytes count in smackfs write functions
security/smack/smackfs.c | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
next parent reply other threads:[~2021-02-16 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7fc1be79-b611-24e9-f2fb-282dd061d755.ref@schaufler-ca.com>
2021-02-16 22:06 ` Casey Schaufler [this message]
2021-02-22 1:20 ` [GIT PULL] Smack patches for v5.12 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=7fc1be79-b611-24e9-f2fb-282dd061d755@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.