From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-17.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03303C6377E for ; Mon, 19 Jul 2021 19:15:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id ED57F610D2 for ; Mon, 19 Jul 2021 19:15:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1384485AbhGSS3u (ORCPT ); Mon, 19 Jul 2021 14:29:50 -0400 Received: from mail.kernel.org ([198.145.29.99]:38778 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1383708AbhGSSJT (ORCPT ); Mon, 19 Jul 2021 14:09:19 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6A9DE60232; Mon, 19 Jul 2021 18:49:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1626720598; bh=rlRvHesfEjeUlsO8Hwp41C5FiOVzlwcYj70KV6aM430=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fSImICV0ySVrVR3XZl3Xw3ry0LlnwYEk3HBW7QQZP1TAwwbEfD4rRqaJDRZECY0ty yj3TjzDU7LJFtDv1ntxUu/Wgy9HkJRlMxH41e3Xx7TgwukhBsUaLjTMzz/laRHyh1j ElmgTbrKCPw+dxvtBExYdrNCh/QFokPSlt+kU6Clpm1wKLriflubYNMLVAx0zwGCVc NLE+EmS1Uq8kf0cJlKN3cWrliF+TM3429JfhU2Xg/XrrLknI9aFneYR42pdMaW5b2q bjGW99cfwJmAbIaalyugU8y0mZd/CQJ7ueKgZ5NMzZImmo0xsN1ianOQBbAbsSgept Uod9M75DXoOHA== Date: Mon, 19 Jul 2021 11:49:57 -0700 From: Jaegeuk Kim To: Chao Yu Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, stable@kernel.org Subject: Re: [f2fs-dev] [PATCH] f2fs: let's keep writing IOs on SBI_NEED_FSCK Message-ID: References: <20210714231850.2567509-1-jaegeuk@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/19, Chao Yu wrote: > On 2021/7/15 7:18, Jaegeuk Kim wrote: > > SBI_NEED_FSCK is an indicator that fsck.f2fs needs to be triggered, so it > > is not fully critical to stop any IO writes. So, let's allow to write data > > instead of reporting EIO forever given SBI_NEED_FSCK. > > Well, it looks we need to check why there is SBI_NEED_FSCK flag. > > If this patch breaks something, how about forcing OPU if SBI_NEED_FSCK > was set? Yea, let me take that. > > > > > Fixes: 955772787667 ("f2fs: drop inplace IO if fs status is abnormal") > > Cc: # v5.13+ > > Signed-off-by: Jaegeuk Kim > > --- > > fs/f2fs/segment.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c > > index 15cc89eef28d..f9b7fb785e1d 100644 > > --- a/fs/f2fs/segment.c > > +++ b/fs/f2fs/segment.c > > @@ -3563,7 +3563,7 @@ int f2fs_inplace_write_data(struct f2fs_io_info *fio) > > goto drop_bio; > > } > > - if (is_sbi_flag_set(sbi, SBI_NEED_FSCK) || f2fs_cp_error(sbi)) { > > + if (f2fs_cp_error(sbi)) { > > err = -EIO; > > goto drop_bio; > > } > >