[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172652224325.3820990.5977903925076414761.git-patchwork-notify@kernel.org>
Date: Mon, 16 Sep 2024 21:30:43 +0000
From: patchwork-bot+f2fs@...nel.org
To: Chao Yu <chao@...nel.org>
Cc: jaegeuk@...nel.org, brauner@...nel.org, jack@...e.cz,
linux-kernel@...r.kernel.org,
syzbot+20d7e439f76bbbd863a7@...kaller.appspotmail.com,
linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to don't set SB_RDONLY in
f2fs_handle_critical_error()
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.org>:
On Tue, 10 Sep 2024 11:07:13 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> ------------[ cut here ]------------
> WARNING: CPU: 1 PID: 58 at kernel/rcu/sync.c:177 rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177
> CPU: 1 UID: 0 PID: 58 Comm: kworker/1:2 Not tainted 6.10.0-syzkaller-12562-g1722389b0d86 #0
> Workqueue: events destroy_super_work
> RIP: 0010:rcu_sync_dtor+0xcd/0x180 kernel/rcu/sync.c:177
> Call Trace:
> percpu_free_rwsem+0x41/0x80 kernel/locking/percpu-rwsem.c:42
> destroy_super_work+0xec/0x130 fs/super.c:282
> process_one_work kernel/workqueue.c:3231 [inline]
> process_scheduled_works+0xa2c/0x1830 kernel/workqueue.c:3312
> worker_thread+0x86d/0xd40 kernel/workqueue.c:3390
> kthread+0x2f0/0x390 kernel/kthread.c:389
> ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to don't set SB_RDONLY in f2fs_handle_critical_error()
https://git.kernel.org/jaegeuk/f2fs/c/930c6ab93492
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists