From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Security Module list
<linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
casey@schaufler-ca.com
Subject: [GIT PULL] Smack patches for v5.4 - retry
Date: Mon, 23 Sep 2019 13:14:33 -0700 [thread overview]
Message-ID: <745ac819-f2ae-4525-1855-535daf783638@schaufler-ca.com> (raw)
Hello Linus
Thank for the instruction. I think this is correct.
I have four patches for v5.4. Nothing is major. All but one are in
response to mechanically detected potential issues. The remaining
patch cleans up kernel-doc notations.
The following changes since commit 0ecfebd2b52404ae0c54a878c872bb93363ada36:
Linux 5.2 (2019-07-07 15:41:56 -0700)
are available in the Git repository at:
https://github.com/cschaufler/smack-next.git tags/smack-for-5.4-rc1
for you to fetch changes up to e5bfad3d7acc5702f32aafeb388362994f4d7bd0:
smack: use GFP_NOFS while holding inode_smack::smk_lock (2019-09-04 09:37:07 -0700)
----------------------------------------------------------------
I have four patches for v5.4. Nothing is major. All but one are in
response to mechanically detected potential issues. The remaining
patch cleans up kernel-doc notations.
----------------------------------------------------------------
Eric Biggers (1):
smack: use GFP_NOFS while holding inode_smack::smk_lock
Jann Horn (1):
Smack: Don't ignore other bprm->unsafe flags if LSM_UNSAFE_PTRACE is set
Jia-Ju Bai (1):
security: smack: Fix possible null-pointer dereferences in smack_socket_sock_rcv_skb()
luanshi (1):
smack: fix some kernel-doc notations
security/smack/smack_access.c | 6 +++---
security/smack/smack_lsm.c | 40 ++++++++++++++++++++--------------------
2 files changed, 23 insertions(+), 23 deletions(-)
next reply other threads:[~2019-09-23 20:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 20:14 Casey Schaufler [this message]
2019-09-23 21:35 ` [GIT PULL] Smack patches for v5.4 - retry Linus Torvalds
2019-09-23 21:38 ` Linus Torvalds
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=745ac819-f2ae-4525-1855-535daf783638@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;
as well as URLs for NNTP newsgroup(s).