From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org,
"Light Hsieh (謝明燈)" <Light.Hsieh@mediatek.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't set RO when shutting down f2fs
Date: Tue, 9 Apr 2024 16:21:58 +0000 [thread overview]
Message-ID: <ZhVrJh3rackEiIfL@google.com> (raw)
In-Reply-To: <2c195fee-c71c-4e44-b24f-9880b3c1b6c4@kernel.org>
On 04/09, Chao Yu wrote:
> On 2024/4/5 3:52, Jaegeuk Kim wrote:
> > Shutdown does not check the error of thaw_super due to readonly, which
> > causes a deadlock like below.
> >
> > f2fs_ioc_shutdown(F2FS_GOING_DOWN_FULLSYNC) issue_discard_thread
> > - bdev_freeze
> > - freeze_super
> > - f2fs_stop_checkpoint()
> > - f2fs_handle_critical_error - sb_start_write
> > - set RO - waiting
> > - bdev_thaw
> > - thaw_super_locked
> > - return -EINVAL, if sb_rdonly()
> > - f2fs_stop_discard_thread
> > -> wait for kthread_stop(discard_thread);
> >
> > Reported-by: "Light Hsieh (謝明燈)" <Light.Hsieh@mediatek.com>
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> > fs/f2fs/super.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> > index df9765b41dac..ba6288e870c5 100644
> > --- a/fs/f2fs/super.c
> > +++ b/fs/f2fs/super.c
> > @@ -4135,9 +4135,16 @@ void f2fs_handle_critical_error(struct f2fs_sb_info *sbi, unsigned char reason,
> > if (shutdown)
> > set_sbi_flag(sbi, SBI_IS_SHUTDOWN);
> > - /* continue filesystem operators if errors=continue */
> > - if (continue_fs || f2fs_readonly(sb))
> > + /*
> > + * Continue filesystem operators if errors=continue. Should not set
> > + * RO by shutdown, since RO bypasses thaw_super which can hang the
> > + * system.
> > + */
> > + if (continue_fs || f2fs_readonly(sb) ||
> > + reason == STOP_CP_REASON_SHUTDOWN) {
> > + f2fs_warn(sbi, "Stopped filesystem due to readon: %d", reason);
> > return;
>
> Do we need to set RO after bdev_thaw() in f2fs_do_shutdown()?
IIRC, shutdown doesn't need to set RO as we stopped the checkpoint.
I'm more concerned on any side effect caused by this RO change.
>
> Thanks,
>
> > + }
> > f2fs_warn(sbi, "Remounting filesystem read-only");
> > /*
_______________________________________________
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-04-09 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 19:52 [f2fs-dev] [PATCH] f2fs: don't set RO when shutting down f2fs Jaegeuk Kim
2024-04-09 3:23 ` Chao Yu
2024-04-09 16:21 ` Jaegeuk Kim [this message]
2024-04-10 1:24 ` Chao Yu
2024-04-09 14:41 ` Daeho Jeong
2024-04-09 16:20 ` [f2fs-dev] [PATCH v2] " Jaegeuk Kim
2024-04-09 23:37 ` Daeho Jeong
2024-04-10 1:25 ` 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=ZhVrJh3rackEiIfL@google.com \
--to=jaegeuk@kernel.org \
--cc=Light.Hsieh@mediatek.com \
--cc=chao@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).