From: "Chen, Yu C" <yu.c.chen@intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: <x86@kernel.org>, <hpa@zytor.com>, <ben.horgan@arm.com>,
<tony.luck@intel.com>, <fustini@kernel.org>,
<fenghuay@nvidia.com>, <peternewman@google.com>,
<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>,
<james.morse@arm.com>, <Dave.Martin@arm.com>,
<babu.moger@amd.com>, <dave.hansen@linux.intel.com>,
<bp@alien8.de>, <tglx@linutronix.de>
Subject: Re: [PATCH v3 8/9] x86/resctrl: Ensure domain fully initialized before placed on RCU list
Date: Sun, 31 May 2026 16:37:37 +0800 [thread overview]
Message-ID: <8d76c93f-7780-4fdd-a3b2-9faa8eeddf57@intel.com> (raw)
In-Reply-To: <4053bd27-bca3-4745-9f34-65843e250f12@intel.com>
On 5/29/2026 12:11 AM, Reinette Chatre wrote:
>
>
> On 5/22/26 12:15 PM, Reinette Chatre wrote:
>> static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, struct list_head *add_pos)
>> @@ -556,14 +554,12 @@ static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, struct
>> return;
>> }
>>
>> - list_add_tail_rcu(&d->hdr.list, add_pos);
>> -
>> err = resctrl_online_mon_domain(r, &d->hdr);
>> if (err) {
>> - list_del_rcu(&d->hdr.list);
>> - synchronize_rcu();
>> l3_mon_domain_free(hw_dom);
>> + return;
>> }
>> + list_add_tail_rcu(&d->hdr.list, add_pos);
>> }
>>
>> static void domain_add_cpu_mon(int cpu, struct rdt_resource *r)
>
> I resubmitted the last three patches of series to obtain Sashiko review [1] and
> respond to that feedback here:
>
> a) Sashiko: "Does this reordering expose the monitor directories to userspace before the
> domain is actually added to the RCU list?"
>
> Yes. As pointed out by Sashiko there is a short time where the monitoring data files
> may be exposed to user space before the monitoring domain is added to the RCU list.
> Also pointed out by Sashiko, if user attempts to read from such file it will return
> -ENOENT.
>
> This behavior looks correct and acceptable to me.
It might not return -ENOENT because the read will be blocked by
cpus_read_lock()
and after the reader has grabed the cpus_read_lock(), the reader will
see the newly
added domain on the list:
CPU 0 (writer) CPU 1 (reader)
========================== ==========================
cpus_write_lock held cpus_read_lock() **BLOCKED**
mkdir mondata files
list_add_tail_rcu()
cpus_write_unlock cpus_read_lock() returns
lock(rdtgroup_mutex)
resctrl_find_domain() **see
a new complete domain**
unlock(rdtgroup_mutex)
cpus_read_unlock()
Reviewed-by: Chen Yu <yu.c.chen@intel.com>
thanks,
Chenyu
next prev parent reply other threads:[~2026-05-31 8:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 19:15 [PATCH v3 0/9] x86,fs/resctrl: Fix long-standing issues Reinette Chatre
2026-05-22 19:15 ` [PATCH v3 1/9] fs/resctrl: Move functions to avoid forward references in subsequent fixes Reinette Chatre
2026-05-28 10:06 ` Ben Horgan
2026-05-22 19:15 ` [PATCH v3 2/9] fs/resctrl: Free mon_data structures on rdt_get_tree() failure Reinette Chatre
2026-05-27 15:18 ` Ben Horgan
2026-05-22 19:15 ` [PATCH v3 3/9] fs/resctrl: Fix use-after-free during unmount Reinette Chatre
2026-05-28 9:45 ` Ben Horgan
2026-05-28 16:09 ` Reinette Chatre
2026-05-28 13:48 ` Chen Yu
2026-05-28 16:09 ` Reinette Chatre
2026-05-22 19:15 ` [PATCH v3 4/9] fs/resctrl: Fix deadlock for errors during mount Reinette Chatre
2026-05-28 10:11 ` Ben Horgan
2026-05-29 14:06 ` Chen, Yu C
2026-05-29 15:53 ` Reinette Chatre
2026-05-31 8:41 ` Chen, Yu C
2026-05-22 19:15 ` [PATCH v3 5/9] fs/resctrl: Prevent use-after-free in rdtgroup_kn_put() Reinette Chatre
2026-05-28 10:51 ` Ben Horgan
2026-05-22 19:15 ` [PATCH v3 6/9] fs/resctrl: Fix pseudo-locking lifetime handling Reinette Chatre
2026-05-28 10:56 ` Ben Horgan
2026-05-28 16:10 ` Reinette Chatre
2026-05-22 19:15 ` [PATCH v3 7/9] fs/resctrl: Prevent deadlock and use-after-free in info file handlers Reinette Chatre
2026-05-22 19:15 ` [PATCH v3 8/9] x86/resctrl: Ensure domain fully initialized before placed on RCU list Reinette Chatre
2026-05-28 16:11 ` Reinette Chatre
2026-05-28 19:04 ` Babu Moger
2026-05-28 20:56 ` Reinette Chatre
2026-05-28 23:10 ` Moger, Babu
2026-05-31 8:37 ` Chen, Yu C [this message]
2026-06-01 15:40 ` Reinette Chatre
2026-05-22 19:15 ` [PATCH v3 9/9] fs/resctrl: Fix UAF from worker threads when domains are removed Reinette Chatre
2026-05-26 15:32 ` Luck, Tony
2026-05-26 17:53 ` Reinette Chatre
2026-05-26 18:27 ` Luck, Tony
2026-05-26 21:05 ` Reinette Chatre
2026-05-26 21:26 ` Luck, Tony
2026-05-27 1:49 ` Reinette Chatre
2026-05-28 16:12 ` Reinette Chatre
2026-05-28 20:08 ` [PATCH v3 0/9] x86,fs/resctrl: Fix long-standing issues Luck, Tony
2026-05-29 18:37 ` Reinette Chatre
2026-05-29 19:06 ` Luck, Tony
2026-05-29 20:19 ` Reinette Chatre
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=8d76c93f-7780-4fdd-a3b2-9faa8eeddf57@intel.com \
--to=yu.c.chen@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=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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