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>,
ChenXiaoSong <chenxiaosong2@huawei.com>,
Jens Axboe <axboe@kernel.dk>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Xiong Zhenwu <xiong.zhenwu@zte.com.cn>
Subject: [GIT PULL] Smack patches for v5.14
Date: Tue, 29 Jun 2021 16:40:31 -0700 [thread overview]
Message-ID: <ababec69-d997-c647-4ac2-2e79dfb3aa40@schaufler-ca.com> (raw)
In-Reply-To: <ababec69-d997-c647-4ac2-2e79dfb3aa40.ref@schaufler-ca.com>
Hello Linus,
Here is the Smack pull request for v5.14.
There is nothing more significant than an improvement to
a byte count check in smackfs. All changes have been in next
for weeks.
Thank you.
--
The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
are available in the Git repository at:
https://github.com/cschaufler/smack-next tags/Smack-for-5.14
for you to fetch changes up to fe6bde732be8c4711a878b11491d9a2749b03909:
Smack: fix doc warning (2021-06-08 10:23:08 -0700)
----------------------------------------------------------------
Minor fixes for v5.14
----------------------------------------------------------------
ChenXiaoSong (1):
Smack: fix doc warning
Jens Axboe (1):
Revert "Smack: Handle io_uring kernel thread privileges"
Tetsuo Handa (1):
smackfs: restrict bytes count in smk_set_cipso()
Xiong Zhenwu (1):
security/smack/: fix misspellings using codespell tool
security/smack/smack_access.c | 10 ++++++----
security/smack/smackfs.c | 4 +++-
2 files changed, 9 insertions(+), 5 deletions(-)
next parent reply other threads:[~2021-06-29 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ababec69-d997-c647-4ac2-2e79dfb3aa40.ref@schaufler-ca.com>
2021-06-29 23:40 ` Casey Schaufler [this message]
2021-06-30 22: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=ababec69-d997-c647-4ac2-2e79dfb3aa40@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=axboe@kernel.dk \
--cc=chenxiaosong2@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
--cc=xiong.zhenwu@zte.com.cn \
/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®