Message-ID: <02723ce8-0ad4-7860-b76c-7d2b30710dcf@huawei.com>
Date:   Fri, 3 Feb 2023 09:10:13 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.0
Subject: Re: [PATCH 4.19 0/3] Backport handling -ESTALE policy update failure
 to 4.19
Content-Language: en-US
To:     Sasha Levin <sashal@kernel.org>
CC:     <stable@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <gregkh@linuxfoundation.org>, <zohar@linux.ibm.com>,
        <paul@paul-moore.com>, <luhuaxin1@huawei.com>
References: <20230201023952.30247-1-guozihua@huawei.com>
 <Y9vw6RhQ6KJ5+E1I@sashalap>
From:   "Guozihua (Scott)" <guozihua@huawei.com>
In-Reply-To: <Y9vw6RhQ6KJ5+E1I@sashalap>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.

-- 
Best
GUO Zihua