From: Reinette Chatre <reinette.chatre@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <tony.luck@intel.com>, <james.morse@arm.com>,
<Dave.Martin@arm.com>, <babu.moger@amd.com>, <tglx@linutronix.de>,
<dave.hansen@linux.intel.com>, <x86@kernel.org>, <hpa@zytor.com>,
<ben.horgan@arm.com>, <fustini@kernel.org>, <fenghuay@nvidia.com>,
<peternewman@google.com>, <yu.c.chen@intel.com>,
<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: Re: [PATCH v7 0/7] x86,fs/resctrl: Fix long-standing issues
Date: Mon, 13 Jul 2026 13:47:55 -0700 [thread overview]
Message-ID: <98a46b67-5259-418f-8a78-e87ca86847b5@intel.com> (raw)
In-Reply-To: <20260713182421.GAalUtVdzT-QmG-nhJ@fat_crate.local>
On 7/13/26 11:29 AM, Borislav Petkov wrote:
> On Mon, Jul 13, 2026 at 10:39:36AM -0700, Reinette Chatre wrote:
>> v6: https://lore.kernel.org/lkml/cover.1783377598.git.reinette.chatre@intel.com/
>> v5: https://lore.kernel.org/lkml/cover.1781029125.git.reinette.chatre@intel.com/
>> v4: https://lore.kernel.org/lkml/cover.1780456704.git.reinette.chatre@intel.com/
>> v3: https://lore.kernel.org/lkml/cover.1779476724.git.reinette.chatre@intel.com/
>> v2: https://lore.kernel.org/lkml/20260515193944.15114-1-tony.luck@intel.com/
>> v1: https://lore.kernel.org/all/20260508182143.14592-1-tony.luck@intel.com/
>>
>> While reviewing the AET series [1] Sashiko reported a deadlock during mount,
>> and a use-after-free when an L3 domain is removed during CPU offline. More issues
>> were uncovered as fixes were developed and reviewed. While the goal is to
>> fix all issues the races surrounding pseudo-locked regions are not yet
>> solved and have been removed from this series (last appearance was in V3 of
>> this series).
>>
>> Applies against v7.2-rc3.
>
> Ack, now that your fixes are upstream, lemme stick those ontop.
Thank you very much Boris.
Reinette
prev parent reply other threads:[~2026-07-13 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 17:39 [PATCH v7 0/7] x86,fs/resctrl: Fix long-standing issues Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 1/7] x86,fs/resctrl: Document safe RCU list traversal Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 2/7] fs/resctrl: Move functions to avoid forward references in subsequent fixes Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 3/7] fs/resctrl: Fix deadlock on errors during mount Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 4/7] fs/resctrl: Prevent use-after-free in rdtgroup_kn_put() Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 5/7] fs/resctrl: Prevent deadlock and use-after-free in info file handlers Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 6/7] x86/resctrl: Ensure domain fully initialized before placed on RCU list Reinette Chatre
2026-07-13 17:39 ` [PATCH v7 7/7] fs/resctrl: Fix UAF from worker threads when domains are removed Reinette Chatre
2026-07-13 18:29 ` [PATCH v7 0/7] x86,fs/resctrl: Fix long-standing issues Borislav Petkov
2026-07-13 20:47 ` Reinette Chatre [this message]
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=98a46b67-5259-418f-8a78-e87ca86847b5@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=fustini@kernel.org \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=peternewman@google.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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