mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Security Module list 
	<linux-security-module@vger.kernel.org>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Maninder Singh <maninder1.s@samsung.com>,
	YueHaibing <yuehaibing@huawei.com>
Subject: [GIT PULL] Smack patches for v5.8
Date: Tue, 2 Jun 2020 13:38:04 -0700	[thread overview]
Message-ID: <02d3f22f-340b-d51b-6dd5-c2011651a145@schaufler-ca.com> (raw)
In-Reply-To: <02d3f22f-340b-d51b-6dd5-c2011651a145.ref@schaufler-ca.com>

Please pull these changes for the Smack LSM. There is a fix for a potential
buffer overflow in smackfs, a fix for an unused variable warning when IPv6
is not configured, removal of a pointless lock in the d_instantiate hook and
some dead code cleanup. All tests pass, and all changes have been in next for
a while.

The following changes since commit 7111951b8d4973bda27ff663f2cf18b663d15b48:

  Linux 5.6 (2020-03-29 15:25:41 -0700)

are available in the Git repository at:

  https://github.com/cschaufler/smack-next tags/Smack-for-5.8

for you to fetch changes up to ef26650a201fbbb4ba90b63a82bf7950f2699a82:

  Smack: Remove unused inline function smk_ad_setfield_u_fs_path_mnt (2020-05-11 10:25:37 -0700)

----------------------------------------------------------------
Arnd Bergmann (1):
      smack: avoid unused 'sip' variable warning

Casey Schaufler (3):
      Smack: slab-out-of-bounds in vsscanf
      Smack:- Remove mutex lock "smk_lock" from inode_smack
      Smack:- Remove redundant inode_smack cache

Maninder Singh (1):
      smack: remove redundant structure variable from header.

YueHaibing (1):
      Smack: Remove unused inline function smk_ad_setfield_u_fs_path_mnt

 security/smack/smack.h     | 12 ------------
 security/smack/smack_lsm.c | 42 +++++++++++-------------------------------
 security/smack/smackfs.c   | 10 ++++++++++
 3 files changed, 21 insertions(+), 43 deletions(-)



       reply	other threads:[~2020-06-02 20:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <02d3f22f-340b-d51b-6dd5-c2011651a145.ref@schaufler-ca.com>
2020-06-02 20:38 ` Casey Schaufler [this message]
2020-06-04 17:35   ` 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=02d3f22f-340b-d51b-6dd5-c2011651a145@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=maninder1.s@samsung.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yuehaibing@huawei.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®