From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: flush inode if atomic file is aborted
Date: Mon, 17 Jul 2023 17:34:21 +0000 [thread overview]
Message-ID: <168961526188.4078.2630269781392789426.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230707141142.2276510-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2023-07-17 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-07 14:11 [f2fs-dev] [PATCH] f2fs: flush inode if atomic file is aborted Jaegeuk Kim
2023-07-11 8:53 ` Chao Yu
2023-07-17 17:34 ` 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=168961526188.4078.2630269781392789426.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+e1246909d526a9d470fa@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).