From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: Security updates for v4.15 and beyond
Date: Wed, 27 Sep 2017 10:03:47 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1709270954470.12698@namei.org> (raw)
In-Reply-To: <f989a3a4-507b-b28b-4eb4-8fd7ece96448@canonical.com>
On Tue, 26 Sep 2017, John Johansen wrote:
> I have to agree with Paul here, unless there are infrastructure
> changes this feels like an extra hop. With next directly pulling
> security (for infrastructure) and LSM changes merge conflicts will
> show up there. At which point we are going to need to coordinate,
> but these should be rare.
Ok, it seems a consensus is emerging to go with Paul's idea of having
larger, frequently updated LSMs merge directly to Linus. If Linus is okay
with that (I'm assuing he will be), then that's how we'll do thing from
now.
Of course, any LSM or other security mechanism is still welcome to be
merged via my tree.
--
James Morris
<jmorris@namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-09-27 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 5:00 [GIT PULL] TPM updates for v4.14 James Morris
2017-09-24 17:53 ` Security updates for v4.15 and beyond Casey Schaufler
2017-09-25 4:59 ` James Morris
2017-09-25 10:32 ` Paul Moore
2017-09-26 19:55 ` John Johansen
2017-09-27 0:03 ` James Morris [this message]
2017-09-27 0:18 ` Casey Schaufler
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=alpine.LRH.2.21.1709270954470.12698@namei.org \
--to=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.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