[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab2f3576-bedd-8c27-5549-f9ff5462aee3@kernel.org>
Date: Thu, 27 Oct 2022 21:31:05 +0800
From: Chao Yu <chao@...nel.org>
To: Yangtao Li <frank.li@...o.com>, jaegeuk@...nel.org
Cc: linux-f2fs-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] f2fs: fix to f2fs_handle_critical_error when
errors=remount-ro
On 2022/10/27 20:08, Yangtao Li wrote:
> When a fatal error occurs in the file system and it is
> remounted to ro mode, the flush thread needs to be stopped.
>
> Fixes: d81ab30e85a5 ("f2fs: support errors=remount-ro|continue|panic mountoption")
Do you mind letting me merge these two patches into original patch?
since original patch is still in dev branch, rather than mainline.
I guess it needs to stop ckpt thread as well...
Thanks,
> Signed-off-by: Yangtao Li <frank.li@...o.com>
> ---
> fs/f2fs/super.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index fc220b5c5599..3a1238a82dc9 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -4017,6 +4017,7 @@ void f2fs_handle_critical_error(struct f2fs_sb_info *sbi, unsigned char reason,
>
> f2fs_stop_gc_thread(sbi);
> f2fs_stop_discard_thread(sbi);
> + f2fs_stop_flush_thread(sbi);
> }
>
> static void f2fs_record_error_work(struct work_struct *work)
Powered by blists - more mailing lists