Re: [PATCH v5 00/11] x86,fs/resctrl: Fix long-standing issues

[Reinette Chatre <reinette.chatre@intel.com>]

Hi Boris,

On 7/1/26 10:09 AM, Borislav Petkov wrote:
> On Tue, Jun 30, 2026 at 03:57:59PM -0700, Borislav Petkov wrote:
>> On Tue, Jun 30, 2026 at 02:47:45PM -0700, Reinette Chatre wrote:
>>> Hi Boris,
>>>
>>> On 6/10/26 12:21 PM, Borislav Petkov wrote:
>>>> On Wed, Jun 10, 2026 at 10:48:06AM -0700, Reinette Chatre wrote:
>>>>> After considering the latest Sashiko feedback and deciding to stop adding
>>>>> new fixes to this series, I do think this series can now be considered as
>>>>> "settled".  If there are no concerns with this series self then I would like
>>>>> to proceed for it to be considered for inclusion.
>>>>
>>>> Ping me after the merge window pls. They'll have to catch the "next train" as
>>>> it is too late now.
>>> I confirmed that this series applies cleanly on top of v7.2-rc1. Could you please
>>> consider it for inclusion during this cycle?
>>>
>>> Thank you very much.
>>
>> Sure, lemme take a look.
> 
> So some of those look to me like urgent material that needs to go to Linus and
> to stable@ now, no?

I agree there are serious issues here. What prevents me from advocating for them
all to go to stable is that the fixes to the intricate races required changes to
resctrl's core locking flows. I absolutely tested and scrutinized these changes but
having them go straight to all the stable kernels feels like a big jump to me.

> Any preferences as to which ones?
The fixes that do not involve locking changes are below. They could be considered
for stable.
1/11: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled
4/11: fs/resctrl: Free mon_data structures on rdt_get_tree() failure
5/11: fs/resctrl: Fix use-after-free during unmount
8/11: fs/resctrl: Fix double-add of pseudo-locked region's RMID to free list

Reinette