From: Hyungjung Joo <jhj140711@gmail.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org,
linux-fsdevel@vger.kernel.org
Cc: jack@suse.cz, greg@kroah.com, linux-kernel@vger.kernel.org,
HyungJung Joo <jhj140711@gmail.com>
Subject: [PATCH] fs/mbcache: cancel shrink work before destroying the cache
Date: Tue, 17 Mar 2026 14:45:56 +0900 [thread overview]
Message-ID: <20260317054556.1821600-1-jhj140711@gmail.com> (raw)
From: HyungJung Joo <jhj140711@gmail.com>
mb_cache_destroy() calls shrinker_free() and then frees all cache
entries and the cache itself, but it does not cancel the pending
c_shrink_work work item first.
If mb_cache_entry_create() schedules c_shrink_work via schedule_work()
and the work item is still pending or running when mb_cache_destroy()
runs, mb_cache_shrink_worker() will access the cache after its memory
has been freed, causing a use-after-free.
This is only reachable by a privileged user (root or CAP_SYS_ADMIN)
who can trigger the last put of a mounted ext2/ext4/ocfs2 filesystem.
Cancel the work item with cancel_work_sync() before calling
shrinker_free(), ensuring the worker has finished and will not be
rescheduled before the cache is torn down.
Signed-off-by: Hyungjung Joo <jhj140711@gmail.com>
---
fs/mbcache.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/mbcache.c b/fs/mbcache.c
index 480d02d6ebf0..2a6319b4072c 100644
--- a/fs/mbcache.c
+++ b/fs/mbcache.c
@@ -406,6 +406,7 @@ void mb_cache_destroy(struct mb_cache *cache)
{
struct mb_cache_entry *entry, *next;
+ cancel_work_sync(&cache->c_shrink_work);
shrinker_free(cache->c_shrink);
/*
--
2.34.1
next reply other threads:[~2026-03-17 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 5:45 Hyungjung Joo [this message]
2026-03-17 14:38 ` [PATCH] fs/mbcache: cancel shrink work before destroying the cache Christian Brauner
2026-03-17 15:43 ` Hyungjung Joo
2026-03-18 9:42 ` Christian Brauner
2026-03-18 18:23 ` Jan Kara
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=20260317054556.1821600-1-jhj140711@gmail.com \
--to=jhj140711@gmail.com \
--cc=brauner@kernel.org \
--cc=greg@kroah.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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