From: Chao Yu <chao@kernel.org>
To: Long Li <leo.lilong@huawei.com>, jaegeuk@kernel.org
Cc: Chao Yu <chao@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, lonuxli.64@gmail.com
Subject: Re: [PATCH v2] f2fs: fix race in concurrent f2fs_stop_gc_thread
Date: Mon, 4 Nov 2024 11:30:38 +0800 [thread overview]
Message-ID: <81a55b36-0a69-42d6-b82a-94499c37a4fd@kernel.org> (raw)
In-Reply-To: <20241104020542.2603607-1-leo.lilong@huawei.com>
On 2024/11/4 10:05, Long Li wrote:
> In my test case, concurrent calls to f2fs shutdown report the following
> stack trace:
>
> Oops: general protection fault, probably for non-canonical address 0xc6cfff63bb5513fc: 0000 [#1] PREEMPT SMP PTI
> CPU: 0 UID: 0 PID: 678 Comm: f2fs_rep_shutdo Not tainted 6.12.0-rc5-next-20241029-g6fb2fa9805c5-dirty #85
> Call Trace:
> <TASK>
> ? show_regs+0x8b/0xa0
> ? __die_body+0x26/0xa0
> ? die_addr+0x54/0x90
> ? exc_general_protection+0x24b/0x5c0
> ? asm_exc_general_protection+0x26/0x30
> ? kthread_stop+0x46/0x390
> f2fs_stop_gc_thread+0x6c/0x110
> f2fs_do_shutdown+0x309/0x3a0
> f2fs_ioc_shutdown+0x150/0x1c0
> __f2fs_ioctl+0xffd/0x2ac0
> f2fs_ioctl+0x76/0xe0
> vfs_ioctl+0x23/0x60
> __x64_sys_ioctl+0xce/0xf0
> x64_sys_call+0x2b1b/0x4540
> do_syscall_64+0xa7/0x240
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> The root cause is a race condition in f2fs_stop_gc_thread() called from
> different f2fs shutdown paths:
>
> [CPU0] [CPU1]
> ---------------------- -----------------------
> f2fs_stop_gc_thread f2fs_stop_gc_thread
> gc_th = sbi->gc_thread
> gc_th = sbi->gc_thread
> kfree(gc_th)
> sbi->gc_thread = NULL
> < gc_th != NULL >
> kthread_stop(gc_th->f2fs_gc_task) //UAF
>
> The commit c7f114d864ac ("f2fs: fix to avoid use-after-free in
> f2fs_stop_gc_thread()") attempted to fix this issue by using a read
> semaphore to prevent races between shutdown and remount threads, but
> it fails to prevent all race conditions.
>
> Fix it by converting to write lock of s_umount in f2fs_do_shutdown().
>
> Fixes: 7950e9ac638e ("f2fs: stop gc/discard thread after fs shutdown")
> Signed-off-by: Long Li <leo.lilong@huawei.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2024-11-04 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 2:05 Long Li
2024-11-04 3:30 ` Chao Yu [this message]
2024-11-07 20:30 ` [f2fs-dev] " patchwork-bot+f2fs
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=81a55b36-0a69-42d6-b82a-94499c37a4fd@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=leo.lilong@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lonuxli.64@gmail.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
/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
all inboxes | Powered by JetHome®