From: Greg KH <greg@kroah.com>
To: Daniel Burgener <dburgener@linux.microsoft.com>
Cc: stable@vger.kernel.org, stephen.smalley.work@gmail.com,
paul@paul-moore.com, selinux@vger.kernel.org, jmorris@namei.org,
sashal@kernel.org
Subject: Re: [PATCH v5.4 0/3] Update SELinuxfs out of tree and then swapover
Date: Fri, 16 Oct 2020 07:00:36 +0200 [thread overview]
Message-ID: <20201016050036.GB461792@kroah.com> (raw)
In-Reply-To: <20201015192956.1797021-1-dburgener@linux.microsoft.com>
On Thu, Oct 15, 2020 at 03:29:53PM -0400, Daniel Burgener wrote:
> This is a backport for stable of my series to fix a race condition in
> selinuxfs during policy load:
>
> selinux: Create function for selinuxfs directory cleanup
> https://lore.kernel.org/selinux/20200819195935.1720168-2-dburgener@linux.microsoft.com/
>
> selinux: Refactor selinuxfs directory populating functions
> https://lore.kernel.org/selinux/20200819195935.1720168-3-dburgener@linux.microsoft.com/
>
> selinux: Standardize string literal usage for selinuxfs directory names
> https://lore.kernel.org/selinux/20200819195935.1720168-4-dburgener@linux.microsoft.com/
>
> selinux: Create new booleans and class dirs out of tree
> https://lore.kernel.org/selinux/20200819195935.1720168-5-dburgener@linux.microsoft.com/
>
> Several changes were necessary to backport. They are detailed in the
> commit message for the third commit in the series. I also dropped the
> original third commit from this because it was only a style change.
As Sasha said, we want to take the original commits as much as possible
to reduce the delta. It is ok to take style changes if other patches
depend on them, because every time we do something that is not upstream,
we create bugs.
So can you redo this series, and backport the original commits, and
provide the ids for them as well?
thanks,
greg k-h
next prev parent reply other threads:[~2020-10-16 5:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 19:29 [PATCH v5.4 0/3] Update SELinuxfs out of tree and then swapover Daniel Burgener
2020-10-15 19:29 ` [PATCH v5.4 1/3] selinux: Create function for selinuxfs directory cleanup Daniel Burgener
2020-10-16 4:59 ` Greg KH
2020-10-15 19:29 ` [PATCH v5.4 2/3] selinux: Refactor selinuxfs directory populating functions Daniel Burgener
2020-10-15 19:29 ` [PATCH v5.4 3/3] selinux: Create new booleans and class dirs out of tree Daniel Burgener
2020-10-16 1:50 ` Sasha Levin
2020-10-16 5:00 ` Greg KH [this message]
2020-10-16 13:05 ` [PATCH v5.4 0/3] Update SELinuxfs out of tree and then swapover Daniel Burgener
2020-10-16 13:55 ` Paul Moore
2020-10-16 14:02 ` Daniel Burgener
2020-10-16 14:22 ` Sasha Levin
2020-10-16 14:36 ` Daniel Burgener
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=20201016050036.GB461792@kroah.com \
--to=greg@kroah.com \
--cc=dburgener@linux.microsoft.com \
--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).