From: patchwork-bot+f2fs@kernel.org
To: Long Li <leo.lilong@huawei.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, yi.zhang@huawei.com,
lonuxli.64@gmail.com, yangerkun@huawei.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix race in concurrent f2fs_stop_gc_thread
Date: Thu, 07 Nov 2024 20:30:37 +0000 [thread overview]
Message-ID: <173101143777.2084993.11494159010925970965.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241104020542.2603607-1-leo.lilong@huawei.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 4 Nov 2024 10:05:42 +0800 you 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
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix race in concurrent f2fs_stop_gc_thread
https://git.kernel.org/jaegeuk/f2fs/c/7b0033dbc483
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-07 20: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
2024-11-07 20:30 ` patchwork-bot+f2fs [this message]
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=173101143777.2084993.11494159010925970965.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=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®