From: sooraj <sooraj20636@gmail.com>
To: linux-mm@kvack.org
Cc: sooraj <sooraj20636@gmail.com>
Subject: [PATCH] mm/bdi: fix race between cgwb_create and conflicting blkcg associations
Date: Tue, 28 Jan 2025 02:52:50 -0500 [thread overview]
Message-ID: <20250128075250.11500-1-sooraj20636@gmail.com> (raw)
Ensure cgwb (cgroup writeback) structures are uniquely associated with a
memcg-blkcg pair to prevent inconsistencies when concurrent cgwb_create
calls race. This resolves a scenario where two threads creating cgwbs
for the same memory cgroup (memcg) but different I/O control groups (blkcg)
could insert conflicting entries.
The fix rechecks for existing cgwbs under the cgwb_lock spinlock after
initial creation. If a conflicting cgwb (same memcg, different blkcg) is
found, it is killed before inserting the new entry. This guarantees a
1:1 relationship between memcg-blkcg pairs and their cgwbs, preserving
system invariants.
Signed-off-by: sooraj <sooraj20636@gmail.com>
---
mm/backing-dev.c | 43 +++++++++++++++++++++++++++++--------------
1 file changed, 29 insertions(+), 14 deletions(-)
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index e61bbb1bd622..67acb565e9a7 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -723,24 +723,39 @@ static int cgwb_create(struct backing_dev_info *bdi,
spin_lock_irqsave(&cgwb_lock, flags);
if (test_bit(WB_registered, &bdi->wb.state) &&
blkcg_cgwb_list->next && memcg_cgwb_list->next) {
- /* we might have raced another instance of this function */
- ret = radix_tree_insert(&bdi->cgwb_tree, memcg_css->id, wb);
- if (!ret) {
- list_add_tail_rcu(&wb->bdi_node, &bdi->wb_list);
- list_add(&wb->memcg_node, memcg_cgwb_list);
- list_add(&wb->blkcg_node, blkcg_cgwb_list);
- blkcg_pin_online(blkcg_css);
- css_get(memcg_css);
- css_get(blkcg_css);
+ /* Re-check under lock to handle races */
+ struct bdi_writeback *existing;
+
+ existing = radix_tree_lookup(&bdi->cgwb_tree, memcg_css->id);
+ if (existing) {
+ if (existing->blkcg_css != blkcg_css) {
+ cgwb_kill(existing);
+ existing = NULL;
+ } else {
+ ret = 0; /* Already exists, treat as success */
+ }
+ }
+
+ if (!existing) {
+ ret = radix_tree_insert(&bdi->cgwb_tree, memcg_css->id, wb);
+ if (!ret) {
+ list_add_tail_rcu(&wb->bdi_node, &bdi->wb_list);
+ list_add(&wb->memcg_node, memcg_cgwb_list);
+ list_add(&wb->blkcg_node, blkcg_cgwb_list);
+ blkcg_pin_online(blkcg_css);
+ css_get(memcg_css);
+ css_get(blkcg_css);
+ }
}
}
spin_unlock_irqrestore(&cgwb_lock, flags);
- if (ret) {
- if (ret == -EEXIST)
- ret = 0;
+
+ if (!ret)
+ goto out_put;
+ if (ret == -EEXIST)
+ ret = 0; /* Lost race, another thread created the same wb */
+ else
goto err_fprop_exit;
- }
- goto out_put;
err_fprop_exit:
bdi_put(bdi);
--
2.45.2
next reply other threads:[~2025-01-27 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:52 sooraj [this message]
2025-01-28 0:53 ` Andrew Morton
2025-01-28 20:48 ` Tejun Heo
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=20250128075250.11500-1-sooraj20636@gmail.com \
--to=sooraj20636@gmail.com \
--cc=linux-mm@kvack.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