All of lore.kernel.org
 help / color / mirror / Atom feed
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 v2 0/4] Update SELinuxfs out of tree and then swapover
Date: Fri, 16 Oct 2020 17:01:20 +0200	[thread overview]
Message-ID: <20201016150120.GB1807231@kroah.com> (raw)
In-Reply-To: <20201016134835.1886478-1-dburgener@linux.microsoft.com>

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?

If it's always been present, why not just use 5.9 to solve it?

thanks,

greg k-h

  parent reply	other threads:[~2020-10-16 15:00 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 ` Greg KH [this message]
2020-10-16 15:38   ` [PATCH v5.4 v2 0/4] Update SELinuxfs out of tree and then swapover Sasha Levin
2020-10-16 15:44     ` Greg KH
2020-10-16 15:49       ` Sasha Levin
2020-10-16 16:01         ` Daniel Burgener
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=20201016150120.GB1807231@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.