[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168961526188.4078.2630269781392789426.git-patchwork-notify@kernel.org>
Date: Mon, 17 Jul 2023 17:34:21 +0000
From: patchwork-bot+f2fs@...nel.org
To: Jaegeuk Kim <jaegeuk@...nel.org>
Cc: linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
syzbot+e1246909d526a9d470fa@...kaller.appspotmail.com,
stable@...r.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: flush inode if atomic file is aborted
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@...nel.org>:
On Fri, 7 Jul 2023 07:11:42 -0700 you wrote:
> Let's flush the inode being aborted atomic operation to avoid stale dirty
> inode during eviction in this call stack:
>
> f2fs_mark_inode_dirty_sync+0x22/0x40 [f2fs]
> f2fs_abort_atomic_write+0xc4/0xf0 [f2fs]
> f2fs_evict_inode+0x3f/0x690 [f2fs]
> ? sugov_start+0x140/0x140
> evict+0xc3/0x1c0
> evict_inodes+0x17b/0x210
> generic_shutdown_super+0x32/0x120
> kill_block_super+0x21/0x50
> deactivate_locked_super+0x31/0x90
> cleanup_mnt+0x100/0x160
> task_work_run+0x59/0x90
> do_exit+0x33b/0xa50
> do_group_exit+0x2d/0x80
> __x64_sys_exit_group+0x14/0x20
> do_syscall_64+0x3b/0x90
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: flush inode if atomic file is aborted
https://git.kernel.org/jaegeuk/f2fs/c/eb4ebfac51db
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