From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: Daeho Jeong <daehojeong@google.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to add missing sb_{start, end}_intwrite() for ckpt thread
Date: Sat, 8 Jun 2024 20:34:47 +0800 [thread overview]
Message-ID: <d38a2712-f7cc-4aea-a343-00335a5215a0@kernel.org> (raw)
In-Reply-To: <20240606095213.4087668-1-chao@kernel.org>
On 2024/6/6 17:52, Chao Yu wrote:
> After commit 261eeb9c1585 ("f2fs: introduce checkpoint_merge mount
> option"), checkpoint can be triggered in background thread, it missed
> to cover f2fs inner checkpoint operation w/ sb_{start,end}_intwrite(),
> fix it.
It needs to use sb_start_intwrite_trylock(), otherwise, it will cause
deadlock as below:
- freeze_super
- sb_wait_write(SB_FREEZE_WRITE)
- sb_wait_write(SB_FREEZE_PAGEFAULT)
- sb_wait_write(SB_FREEZE_FS)
- sync
- iterate_supers
- super_lock_shared
- down_read(&sb->s_umount)
- sync_fs_one_sb
- f2fs_sync_fs
- f2fs_issue_checkpoint
- wait_for_completion
- issue_checkpoint_thread
- sb_start_intwrite(sbi->sb);
- thaw_super
- super_lock_excl
- down_write(&sb->s_umount)
Thanks,
>
> Fixes: 261eeb9c1585 ("f2fs: introduce checkpoint_merge mount option")
> Cc: Daeho Jeong <daehojeong@google.com>
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
> fs/f2fs/checkpoint.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> index 55d444bec5c0..66eaad591b60 100644
> --- a/fs/f2fs/checkpoint.c
> +++ b/fs/f2fs/checkpoint.c
> @@ -1828,8 +1828,11 @@ static int issue_checkpoint_thread(void *data)
> if (kthread_should_stop())
> return 0;
>
> - if (!llist_empty(&cprc->issue_list))
> + if (!llist_empty(&cprc->issue_list)) {
> + sb_start_intwrite(sbi->sb);
> __checkpoint_and_complete_reqs(sbi);
> + sb_end_intwrite(sbi->sb);
> + }
>
> wait_event_interruptible(*q,
> kthread_should_stop() || !llist_empty(&cprc->issue_list));
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-06-08 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 9:52 [f2fs-dev] [PATCH 1/2] f2fs: fix to add missing sb_{start, end}_intwrite() for ckpt thread Chao Yu
2024-06-06 9:52 ` [f2fs-dev] [PATCH 2/2] f2fs: fix to use sb_{start, end}_intwrite{_trylock, }() in gc_thread_func() Chao Yu
2024-06-19 14:14 ` Chao Yu
2024-06-08 12:34 ` Chao Yu [this message]
2024-06-10 15:10 ` [f2fs-dev] [PATCH 1/2] f2fs: fix to add missing sb_{start, end}_intwrite() for ckpt thread Daeho Jeong
2024-06-24 1:58 ` Chao Yu
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=d38a2712-f7cc-4aea-a343-00335a5215a0@kernel.org \
--to=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).