From: Jeongjun Park <aha310510@gmail.com>
To: dennis@kernel.org, tj@kernel.org, cl@linux.com,
akpm@linux-foundation.org
Cc: jack@suse.cz, hughd@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Jeongjun Park <aha310510@gmail.com>
Subject: [PATCH] lib/percpu_counter: fix data race in __percpu_counter_limited_add()
Date: Tue, 6 May 2025 19:24:02 +0900 [thread overview]
Message-ID: <20250506102402.88141-1-aha310510@gmail.com> (raw)
The following data-race was found in __percpu_counter_limited_add():
==================================================================
BUG: KCSAN: data-race in __percpu_counter_limited_add / __percpu_counter_limited_add
write to 0xffff88801f417e50 of 8 bytes by task 6663 on cpu 0:
__percpu_counter_limited_add+0x388/0x4a0 lib/percpu_counter.c:386
percpu_counter_limited_add include/linux/percpu_counter.h:77 [inline]
shmem_inode_acct_blocks+0x10e/0x230 mm/shmem.c:233
shmem_alloc_and_add_folio mm/shmem.c:1923 [inline]
shmem_get_folio_gfp.constprop.0+0x87f/0xc90 mm/shmem.c:2533
shmem_get_folio mm/shmem.c:2639 [inline]
....
read to 0xffff88801f417e50 of 8 bytes by task 6659 on cpu 1:
__percpu_counter_limited_add+0xc8/0x4a0 lib/percpu_counter.c:344
percpu_counter_limited_add include/linux/percpu_counter.h:77 [inline]
shmem_inode_acct_blocks+0x10e/0x230 mm/shmem.c:233
shmem_alloc_and_add_folio mm/shmem.c:1923 [inline]
shmem_get_folio_gfp.constprop.0+0x87f/0xc90 mm/shmem.c:2533
shmem_get_folio mm/shmem.c:2639 [inline]
....
value changed: 0x000000000000396d -> 0x000000000000398e
==================================================================
__percpu_counter_limited_add() should protect fbc via raw_spin_lock(),
but it calls spinlock in the wrong place. This causes a data-race,
so we need to fix it to call raw_spin_lock() a bit earlier.
Fixes: beb986862844 ("shmem,percpu_counter: add _limited_add(fbc, limit, amount)")
Signed-off-by: Jeongjun Park <aha310510@gmail.com>
---
lib/percpu_counter.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/percpu_counter.c b/lib/percpu_counter.c
index 2891f94a11c6..17f9fc12b409 100644
--- a/lib/percpu_counter.c
+++ b/lib/percpu_counter.c
@@ -336,6 +336,7 @@ bool __percpu_counter_limited_add(struct percpu_counter *fbc,
return true;
local_irq_save(flags);
+ raw_spin_lock(&fbc->lock);
unknown = batch * num_online_cpus();
count = __this_cpu_read(*fbc->counters);
@@ -344,11 +345,10 @@ bool __percpu_counter_limited_add(struct percpu_counter *fbc,
((amount > 0 && fbc->count + unknown <= limit) ||
(amount < 0 && fbc->count - unknown >= limit))) {
this_cpu_add(*fbc->counters, amount);
- local_irq_restore(flags);
- return true;
+ good = true;
+ goto out;
}
- raw_spin_lock(&fbc->lock);
count = fbc->count + amount;
/* Skip percpu_counter_sum() when safe */
--
next reply other threads:[~2025-05-06 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 10:24 Jeongjun Park [this message]
2025-05-06 11:56 ` Mateusz Guzik
2025-05-07 0:10 ` Andrew Morton
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=20250506102402.88141-1-aha310510@gmail.com \
--to=aha310510@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@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