From: Mimi Zohar <zohar@linux.ibm.com>
To: James Morris <jmorris@namei.org>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: Re: [GIT PULL] security: general updates for v4.21
Date: Tue, 08 Jan 2019 16:56:35 -0500 [thread overview]
Message-ID: <1546984595.19931.158.camel@linux.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1901080840080.2451@namei.org>
On Tue, 2019-01-08 at 08:45 +1100, James Morris wrote:
> > Included in this open window are a number of LSM changes, which were
> > not posted on the LSM mailing list and are not being upstreamed via
> > the LSMs.
>
> If you see changes doing this, please call them out. Any changes to LSM
> need to be cc'd at least to the LSM mailing list.
Sure. I'm referring to Al's match_token() and other changes, which I
only learned about when Linus reviewed Eric Bigger's patch "KEYS: fix
parsing invalid pkey info string".
169d68efb03b selinux: switch away from match_token()
c3300aaf95fb smack: get rid of match_token()
Mimi
next prev parent reply other threads:[~2019-01-08 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 19:55 [GIT PULL] security: general updates for v4.21 James Morris
2018-12-27 20:07 ` Linus Torvalds
2018-12-29 3:11 ` James Morris
2018-12-29 3:39 ` Linus Torvalds
2018-12-29 4:09 ` James Morris
2018-12-29 4:15 ` Linus Torvalds
2018-12-29 18:34 ` Casey Schaufler
2018-12-30 2:44 ` Mimi Zohar
2019-01-07 21:45 ` James Morris
2019-01-08 21:56 ` Mimi Zohar [this message]
2018-12-27 22:05 ` 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=1546984595.19931.158.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zohar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).