From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Daniel Burgener <dburgener@linux.microsoft.com>, selinux@vger.kernel.org
Cc: omosnace@redhat.com, paul@paul-moore.com,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 1/4] selinux: Create function for selinuxfs directory cleanup
Date: Thu, 20 Aug 2020 10:53:33 -0400 [thread overview]
Message-ID: <cc792e5a-b74f-3d0c-c52c-9fdaa6efc0ca@gmail.com> (raw)
In-Reply-To: <20200819195935.1720168-2-dburgener@linux.microsoft.com>
On 8/19/20 3:59 PM, 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>
Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
next prev parent reply other threads:[~2020-08-20 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 19:59 [PATCH v3 0/4] Update SELinuxfs out of tree and then swapover Daniel Burgener
2020-08-19 19:59 ` [PATCH v3 1/4] selinux: Create function for selinuxfs directory cleanup Daniel Burgener
2020-08-20 14:53 ` Stephen Smalley [this message]
2020-08-21 13:43 ` Paul Moore
2020-08-19 19:59 ` [PATCH v3 2/4] selinux: Refactor selinuxfs directory populating functions Daniel Burgener
2020-08-20 14:55 ` Stephen Smalley
2020-08-21 13:43 ` Paul Moore
2020-08-19 19:59 ` [PATCH v3 3/4] selinux: Standardize string literal usage for selinuxfs directory names Daniel Burgener
2020-08-20 14:56 ` Stephen Smalley
2020-08-21 13:44 ` Paul Moore
2020-08-19 19:59 ` [PATCH v3 4/4] selinux: Create new booleans and class dirs out of tree Daniel Burgener
2020-08-20 15:23 ` Stephen Smalley
2020-08-21 13:44 ` 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=cc792e5a-b74f-3d0c-c52c-9fdaa6efc0ca@gmail.com \
--to=stephen.smalley.work@gmail.com \
--cc=dburgener@linux.microsoft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).