From: Greg KH <gregkh@linuxfoundation.org>
To: "Guozihua (Scott)" <guozihua@huawei.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.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: Fri, 3 Feb 2023 08:44:51 +0100 [thread overview]
Message-ID: <Y9y7c5sEX5phLybE@kroah.com> (raw)
In-Reply-To: <02723ce8-0ad4-7860-b76c-7d2b30710dcf@huawei.com>
On Fri, Feb 03, 2023 at 09:10:13AM +0800, Guozihua (Scott) wrote:
> On 2023/2/3 1:20, Sasha Levin wrote:
> > 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?
> >
> Hi Sasha.
>
> The issue mentioned in this patch was fixed already in the newer kernel.
> All three patches here are backports from mainline.
Ok, now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-02-03 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 2:39 [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure to 4.19 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 ` [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure to 4.19 Sasha Levin
2023-02-03 1:10 ` Guozihua (Scott)
2023-02-03 7:44 ` Greg KH [this message]
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=Y9y7c5sEX5phLybE@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=guozihua@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luhuaxin1@huawei.com \
--cc=paul@paul-moore.com \
--cc=sashal@kernel.org \
--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 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.