From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH] ima: require secure_boot rules in lockdown mode
Date: Fri, 10 Nov 2017 00:28:40 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711100020240.514@localhost> (raw)
In-Reply-To: <1510196818.4484.120.camel@linux.vnet.ibm.com>
On Wed, 8 Nov 2017, Mimi Zohar wrote:
> > So since those patches are now in James tree, you should drop them from
> > the integrity tree.
>
> Ok, I had been planning on sending an independent pull request to
> Linus, as requested.
That was not requested. Linus wants separate branches to pull from, but
this does not mean separate trees. The x86 and some other subsystems use
separate branches in the same tree, which is the model we're now using
generally with the security subsystem.
It's _also_ possible to send pull requests independently (which is what
the SELinux and AppArmor maintainers decided to do), although that was not
what Linus was asking for.
It's up to you if you want to send pull requests directly to Linus or
continue to merge via the security tree.
- James
--
James Morris
<james.l.morris@oracle.com>
--
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-11-09 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 15:59 [RFC PATCH] ima: require secure_boot rules in lockdown mode Mimi Zohar
2017-10-30 15:55 ` David Howells
2017-10-30 17:00 ` Mimi Zohar
2017-10-30 17:05 ` David Howells
2017-10-30 17:39 ` Mimi Zohar
2017-10-31 3:25 ` James Morris
2017-11-08 20:46 ` Mimi Zohar
2017-11-08 20:53 ` Stephen Rothwell
2017-11-08 21:04 ` Mimi Zohar
2017-11-08 23:26 ` Stephen Rothwell
2017-11-09 3:06 ` Mimi Zohar
2017-11-09 13:28 ` James Morris [this message]
2017-11-09 13:46 ` Mimi Zohar
2017-11-09 19:17 ` James Morris
2017-11-02 17:11 ` David Howells
2017-11-02 21:30 ` Mimi Zohar
2017-11-02 21:43 ` David Howells
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.LFD.2.20.1711100020240.514@localhost \
--to=james.l.morris@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).