From: Greg KH <gregkh@linuxfoundation.org>
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 1/3] selinux: Create function for selinuxfs directory cleanup
Date: Fri, 16 Oct 2020 06:59:27 +0200 [thread overview]
Message-ID: <20201016045927.GA461792@kroah.com> (raw)
In-Reply-To: <20201015192956.1797021-2-dburgener@linux.microsoft.com>
On Thu, Oct 15, 2020 at 03:29:54PM -0400, Daniel Burgener wrote:
> Separating the cleanup from the creation will simplify two things in
> future patches in this series. First, the creation can be made generic,
> to create directories not tied to the selinux_fs_info structure. Second,
> we will ultimately want to reorder creation and deletion so that the
> deletions aren't performed until the new directory structures have already
> been moved into place.
>
> Signed-off-by: Daniel Burgener <dburgener@linux.microsoft.com>
> ---
> security/selinux/selinuxfs.c | 39 +++++++++++++++++++++++-------------
> 1 file changed, 25 insertions(+), 14 deletions(-)
What is the git commit id of this patch upstream in Linus's tree?
Same for the other 2, we need those ids.
thanks,
gre gk-h
next prev parent reply other threads:[~2020-10-16 4:59 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 [this message]
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 ` [PATCH v5.4 0/3] Update SELinuxfs out of tree and then swapover Greg KH
2020-10-16 13:05 ` 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=20201016045927.GA461792@kroah.com \
--to=gregkh@linuxfoundation.org \
--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