mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: GUO Zihua <guozihua@huawei.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	gregkh@linuxfoundation.org, zohar@linux.ibm.com,
	paul@paul-moore.com, luhuaxin1@huawei.com
Subject: Re: [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure to 4.19
Date: Thu, 2 Feb 2023 12:20:41 -0500	[thread overview]
Message-ID: <Y9vw6RhQ6KJ5+E1I@sashalap> (raw)
In-Reply-To: <20230201023952.30247-1-guozihua@huawei.com>

On Wed, Feb 01, 2023 at 10:39:49AM +0800, GUO Zihua wrote:
>This series backports patches in order to resolve the issue discussed here:
>https://lore.kernel.org/selinux/389334fe-6e12-96b2-6ce9-9f0e8fcb85bf@huawei.com/
>
>This required backporting the non-blocking LSM policy update mechanism
>prerequisite patches.

Do we not need this on newer kernels? Why only 4.19?

-- 
Thanks,
Sasha

  parent reply	other threads:[~2023-02-02 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01  2:39 GUO Zihua
2023-02-01  2:39 ` [PATCH 4.19 1/3] LSM: switch to blocking policy update notifiers GUO Zihua
2023-02-01  2:39 ` [PATCH 4.19 2/3] ima: use the lsm policy update notifier GUO Zihua
2023-02-01  2:39 ` [PATCH 4.19 3/3] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2023-02-02 17:20 ` Sasha Levin [this message]
2023-02-03  1:10   ` [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure to 4.19 Guozihua (Scott)
2023-02-03  7:44     ` Greg KH
2023-02-03  7:49       ` Greg KH
2023-02-03  7:54         ` Greg KH
2023-02-06  2:55           ` Guozihua (Scott)

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=Y9vw6RhQ6KJ5+E1I@sashalap \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=guozihua@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luhuaxin1@huawei.com \
    --cc=paul@paul-moore.com \
    --cc=stable@vger.kernel.org \
    --cc=zohar@linux.ibm.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

all inboxes | Powered by JetHome®