From: Daniel Burgener <dburgener@linux.microsoft.com>
To: Sasha Levin <sashal@kernel.org>, Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, stephen.smalley.work@gmail.com,
paul@paul-moore.com, selinux@vger.kernel.org, jmorris@namei.org
Subject: Re: [PATCH v5.4 v2 0/4] Update SELinuxfs out of tree and then swapover
Date: Fri, 16 Oct 2020 12:01:02 -0400 [thread overview]
Message-ID: <213527b2-87ce-01bf-0699-b82fa65dc91e@linux.microsoft.com> (raw)
In-Reply-To: <20201016154936.GB2415204@sasha-vm>
On 10/16/20 11:49 AM, Sasha Levin wrote:
> On Fri, Oct 16, 2020 at 05:44:43PM +0200, Greg KH wrote:
>> On Fri, Oct 16, 2020 at 11:38:23AM -0400, Sasha Levin wrote:
>>> On Fri, Oct 16, 2020 at 05:01:20PM +0200, Greg KH wrote:
>>> > On Fri, Oct 16, 2020 at 09:48:31AM -0400, Daniel Burgener wrote:
>>> > > v2: Include all commits from original series, and include commit
>>> ids
>>> > >
>>> > > This is a backport for stable of my series to fix a race
>>> condition in
>>> > > selinuxfs during policy load:
>>> >
>>> > Has this race condition always been present, or is this a regression
>>> > that is being fixed from previously working kernels?
>>>
>>> So this issue has always been there, but:
>>>
>>> > If it's always been present, why not just use 5.9 to solve it?
>>>
>>> Because it was merged for 5.10 rather than 5.9, which is a few months
>>> out, so Daniel is looking to see if we can have it in 5.8/5.4 to close
>>> the gap.
>>
>> I would have to wait for 5.10-rc1 at the earliest, and get the selinux
>> maintainers ack for this :)
>
> No objections; if the selinux folks feel unhappy with this it'll just
> wait for 5.10.
>
Yes, that's fine from my end as well. We can carry this series out of
tree in the interim. Thanks!
-Daniel
next prev parent reply other threads:[~2020-10-16 16:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 13:48 [PATCH v5.4 v2 0/4] Update SELinuxfs out of tree and then swapover Daniel Burgener
2020-10-16 13:48 ` [PATCH v5.4 v2 1/4] selinux: Create function for selinuxfs directory cleanup Daniel Burgener
2020-10-16 13:48 ` [PATCH v5.4 v2 2/4] selinux: Refactor selinuxfs directory populating functions Daniel Burgener
2020-10-16 13:48 ` [PATCH v5.4 v2 3/4] selinux: Standardize string literal usage for selinuxfs directory names Daniel Burgener
2020-10-16 13:48 ` [PATCH v5.4 v2 4/4] selinux: Create new booleans and class dirs out of tree Daniel Burgener
2020-10-16 15:01 ` [PATCH v5.4 v2 0/4] Update SELinuxfs out of tree and then swapover Greg KH
2020-10-16 15:38 ` Sasha Levin
2020-10-16 15:44 ` Greg KH
2020-10-16 15:49 ` Sasha Levin
2020-10-16 16:01 ` Daniel Burgener [this message]
2020-10-16 22:56 ` Paul Moore
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=213527b2-87ce-01bf-0699-b82fa65dc91e@linux.microsoft.com \
--to=dburgener@linux.microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=paul@paul-moore.com \
--cc=sashal@kernel.org \
--cc=selinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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).