From: Mimi Zohar <zohar@linux.ibm.com>
To: Paul Moore <paul@paul-moore.com>,
Tushar Sugandhi <tusharsu@linux.microsoft.com>
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>,
SELinux <selinux@vger.kernel.org>,
Tyler Hicks <tyhicks@linux.microsoft.com>,
Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
linux-integrity@vger.kernel.org
Subject: Re: [RFC] Finding the right target branch for patches that span IMA and SeLinux
Date: Tue, 03 Nov 2020 07:25:54 -0500 [thread overview]
Message-ID: <9bdf80cc1ab1c6344ff2cf88130aff3f87a7247b.camel@linux.ibm.com> (raw)
In-Reply-To: <CAHC9VhT36qSJvhH5CFwixdT8tzH2bqfvaDa6nPZt1rmOKOr_kQ@mail.gmail.com>
On Mon, 2020-11-02 at 22:11 -0500, Paul Moore wrote:
> On Sat, Oct 31, 2020 at 11:08 PM Tushar Sugandhi
>
> Can you and Lakshmi help me better understand the state of the
> SELinux/IMA patches? I see that you included Lakshmi's SELinux/IMA
> patch in your last patchset, and it appears to have included feedback
> from Stephen's last review. Is it your intent to continue to submit
> the SELinux/IMA patch as part of a larger patchset, or do you plan to
> split that back out into a standalone patch?
Paul, I've asked Tushar and Lakshmi to first define "critical data"
and then include at least one example of measuring "critical data" to
simplify review. As the SELinux patch is the first example, there is a
dependency on the rest of the patch set.
thanks,
Mimi
next prev parent reply other threads:[~2020-11-03 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 23:33 [RFC] Finding the right target branch for patches that span IMA and SeLinux Tushar Sugandhi
2020-10-30 0:32 ` Mimi Zohar
2020-10-30 16:43 ` Tushar Sugandhi
2020-10-30 20:37 ` Paul Moore
2020-11-01 3:08 ` Tushar Sugandhi
2020-11-02 16:35 ` Mimi Zohar
2020-11-02 20:38 ` Tushar Sugandhi
2020-11-03 3:11 ` Paul Moore
2020-11-03 12:25 ` Mimi Zohar [this message]
2020-11-03 18:57 ` Lakshmi Ramasubramanian
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=9bdf80cc1ab1c6344ff2cf88130aff3f87a7247b.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=nramas@linux.microsoft.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tusharsu@linux.microsoft.com \
--cc=tyhicks@linux.microsoft.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