From: Abhishek Kumar <abhishek_sts8@yahoo.com>
To: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
syzbot+606f94dfeaaa45124c90@syzkaller.appspotmail.com,
Abhishek Kumar <abhishek_sts8@yahoo.com>
Subject: [PATCH] mm: fix data race in __filemap_remove_folio / folio_mapping
Date: Mon, 23 Mar 2026 00:33:19 +0530 [thread overview]
Message-ID: <20260322190319.85301-1-abhishek_sts8@yahoo.com> (raw)
In-Reply-To: 20260322190319.85301-1-abhishek_sts8.ref@yahoo.com
KCSAN reports a data race between page_cache_delete() and
folio_mapping():
page_cache_delete() performs a plain store to folio->mapping:
folio->mapping = NULL;
folio_mapping() performs a plain load from folio->mapping:
mapping = folio->mapping;
page_cache_delete() is called from the truncation path under the i_pages
xarray lock, while folio_mapping() is called from the reclaim path
(evict_folios -> folio_evictable -> folio_mapping) under only
rcu_read_lock() without the xarray lock.
The race is benign since the reclaim path tolerates stale values --
reading a stale non-NULL mapping simply results in a suboptimal eviction
decision. However, the plain accesses risk store/load tearing and allow
the compiler to perform harmful optimizations (merging, elision, or
fission of the accesses).
Fix this by using WRITE_ONCE() in page_cache_delete() and READ_ONCE()
in folio_mapping() to prevent compiler misbehavior and silence the KCSAN
report.
Fixes: 2f52578f9c64 ("mm/util: Add folio_mapping() and folio_file_mapping()")
Reported-by: syzbot+606f94dfeaaa45124c90@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=606f94dfeaaa45124c90
Signed-off-by: Abhishek Kumar <abhishek_sts8@yahoo.com>
---
mm/filemap.c | 2 +-
mm/util.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index 406cef06b684..bba669bd114f 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -142,7 +142,7 @@ static void page_cache_delete(struct address_space *mapping,
xas_store(&xas, shadow);
xas_init_marks(&xas);
- folio->mapping = NULL;
+ WRITE_ONCE(folio->mapping, NULL);
/* Leave folio->index set: truncation lookup relies upon it */
mapping->nrpages -= nr;
}
diff --git a/mm/util.c b/mm/util.c
index b05ab6f97e11..5ecb19ddf026 100644
--- a/mm/util.c
+++ b/mm/util.c
@@ -700,7 +700,7 @@ struct address_space *folio_mapping(const struct folio *folio)
if (unlikely(folio_test_swapcache(folio)))
return swap_address_space(folio->swap);
- mapping = folio->mapping;
+ mapping = READ_ONCE(folio->mapping);
if ((unsigned long)mapping & FOLIO_MAPPING_FLAGS)
return NULL;
--
2.43.0
next parent reply other threads:[~2026-03-22 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260322190319.85301-1-abhishek_sts8.ref@yahoo.com>
2026-03-22 19:03 ` Abhishek Kumar [this message]
2026-03-23 3:57 ` [PATCH] mm: fix data race in __filemap_remove_folio / folio_mapping Matthew Wilcox
2026-03-23 10:47 ` Pedro Falcato
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=20260322190319.85301-1-abhishek_sts8@yahoo.com \
--to=abhishek_sts8@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+606f94dfeaaa45124c90@syzkaller.appspotmail.com \
--cc=willy@infradead.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