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=-13.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE autolearn=unavailable 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 01615C07E95 for ; Wed, 7 Jul 2021 17:48:32 +0000 (UTC) Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id AEA7961CC1 for ; Wed, 7 Jul 2021 17:48:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AEA7961CC1 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-f2fs-devel-bounces@lists.sourceforge.net Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1m1Bev-0004up-NB; Wed, 07 Jul 2021 17:48:29 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m1Beu-0004uj-II for linux-f2fs-devel@lists.sourceforge.net; Wed, 07 Jul 2021 17:48:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=QDpw94IDdsIPxw94fT7s675dIqF9556kzYGxyyD2gTE=; b=loWwDKPGfYSVI1EKGiti+hbvn6 kETMVjVclTOjsfbbir68Ut5lAzveubRUegoug80GKixfGn1TEJAuN7v383JcvHN/jsGlPG+b2LS3n 4x493PEPIexNd2ibbO0kK6HFQRq+gt7wxwcobVFRDnQR85pYUJMxyYldwxd1fOJFDKyM=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To :From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=QDpw94IDdsIPxw94fT7s675dIqF9556kzYGxyyD2gTE=; b=RUpY0pjbDgw0BLd8Z+iyVHQ9l0 Y16CzBv6gCHAnMW9rilVWcCdd17eSvdpjXm3whhSQggH97jz068MNd/HL/yNqdpdh2ieWA/7pm/f7 /ZiLHxMyHJHN7CX3v1VMhPHpx6dDE33VVfakXr9Rp8dNJ8jKVUdtuYzInLRTda51meOU=; Received: from mail.kernel.org ([198.145.29.99]) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) id 1m1Bem-00EUi9-Ce for linux-f2fs-devel@lists.sourceforge.net; Wed, 07 Jul 2021 17:48:28 +0000 Received: by mail.kernel.org (Postfix) with ESMTPSA id DBB7661CC9; Wed, 7 Jul 2021 17:48:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1625680094; bh=vvwMXjdpAOUVfaE6QIqNUFd4xufRLAI7AFwFrBKqC0g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=bABlUhNq8rfmkhrO4NWIKZqs7jmr3Rn8VQ9L/YIAnMZHRnQ1AkDX9bN5Rg3itU8TR 7Q03Ey8cAR8oXT4O4we6clJedusLIY0DCYFMRs9s6m0/FzTwPW9NB+IT36qnD+JKrr fk8RT0lnaDcAc7fccsU9Jup37Zssth6ruS9+kzOQBTQjWntHk/TrXb05dr7I3bV47A FhexIQDJUf62X9AIkesGfSx0W3gikXXrcveU+BmTkUCuzPGlqaSam5zrRnPwuOzokn 2Pg0B0imlp5RAYEuUORh4k03ki+4DRXf+e85/wlVCkU3L6Te86Qq6rKo3S/g8FS4WM Vb4NjpxV2SDsA== Date: Wed, 7 Jul 2021 10:48:12 -0700 From: Jaegeuk Kim To: Chao Yu Message-ID: References: <20210601101024.119356-1-yuchao0@huawei.com> <648a96f7-2c83-e9ed-0cbd-4ee8e4797724@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Headers-End: 1m1Bem-00EUi9-Ce Subject: Re: [f2fs-dev] [PATCH v2 RFC] f2fs: fix to force keeping write barrier for strict fsync mode X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On 07/02, Chao Yu wrote: > On 2021/7/2 9:32, Jaegeuk Kim wrote: > > On 07/02, Chao Yu wrote: > > > On 2021/7/2 1:10, Jaegeuk Kim wrote: > > > > On 06/01, Chao Yu wrote: > > > > > [1] https://www.mail-archive.com/linux-f2fs-devel@lists.sourceforge.net/msg15126.html > > > > > > > > > > As [1] reported, if lower device doesn't support write barrier, in below > > > > > case: > > > > > > > > > > - write page #0; persist > > > > > - overwrite page #0 > > > > > - fsync > > > > > - write data page #0 OPU into device's cache > > > > > - write inode page into device's cache > > > > > - issue flush > > > > > > > > Well, we have preflush for node writes, so I don't think this is the case. > > > > > > > > fio.op_flags |= REQ_PREFLUSH | REQ_FUA; > > > > > > This is only used for atomic write case, right? > > > > > > I mean the common case which is called from f2fs_issue_flush() in > > > f2fs_do_sync_file(). > > > > How about adding PREFLUSH when writing node blocks aligned to the above set? > > You mean implementation like v1 as below? > > https://lore.kernel.org/linux-f2fs-devel/20200120100045.70210-1-yuchao0@huawei.com/ Yea, I think so. :P > > Thanks, > > > > > > > > > And please see do_checkpoint(), we call f2fs_flush_device_cache() and > > > commit_checkpoint() separately to keep persistence order of CP datas. > > > > > > See commit 46706d5917f4 ("f2fs: flush cp pack except cp pack 2 page at first") > > > for details. > > > > > > Thanks, > > > > > > > > > > > > > > > > > If SPO is triggered during flush command, inode page can be persisted > > > > > before data page #0, so that after recovery, inode page can be recovered > > > > > with new physical block address of data page #0, however there may > > > > > contains dummy data in new physical block address. > > > > > > > > > > Then what user will see is: after overwrite & fsync + SPO, old data in > > > > > file was corrupted, if any user do care about such case, we can suggest > > > > > user to use STRICT fsync mode, in this mode, we will force to trigger > > > > > preflush command to persist data in device cache in prior to node > > > > > writeback, it avoids potential data corruption during fsync(). > > > > > > > > > > Signed-off-by: Chao Yu > > > > > --- > > > > > v2: > > > > > - fix this by adding additional preflush command rather than using > > > > > atomic write flow. > > > > > fs/f2fs/file.c | 14 ++++++++++++++ > > > > > 1 file changed, 14 insertions(+) > > > > > > > > > > diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c > > > > > index 7d5311d54f63..238ca2a733ac 100644 > > > > > --- a/fs/f2fs/file.c > > > > > +++ b/fs/f2fs/file.c > > > > > @@ -301,6 +301,20 @@ static int f2fs_do_sync_file(struct file *file, loff_t start, loff_t end, > > > > > f2fs_exist_written_data(sbi, ino, UPDATE_INO)) > > > > > goto flush_out; > > > > > goto out; > > > > > + } else { > > > > > + /* > > > > > + * for OPU case, during fsync(), node can be persisted before > > > > > + * data when lower device doesn't support write barrier, result > > > > > + * in data corruption after SPO. > > > > > + * So for strict fsync mode, force to trigger preflush to keep > > > > > + * data/node write order to avoid potential data corruption. > > > > > + */ > > > > > + if (F2FS_OPTION(sbi).fsync_mode == FSYNC_MODE_STRICT && > > > > > + !atomic) { > > > > > + ret = f2fs_issue_flush(sbi, inode->i_ino); > > > > > + if (ret) > > > > > + goto out; > > > > > + } > > > > > } > > > > > go_write: > > > > > /* > > > > > -- > > > > > 2.29.2 _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel 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.4 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 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 E8684C07E95 for ; Wed, 7 Jul 2021 17:48:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CF4A561CCB for ; Wed, 7 Jul 2021 17:48:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231235AbhGGRu4 (ORCPT ); Wed, 7 Jul 2021 13:50:56 -0400 Received: from mail.kernel.org ([198.145.29.99]:50010 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231205AbhGGRuy (ORCPT ); Wed, 7 Jul 2021 13:50:54 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id DBB7661CC9; Wed, 7 Jul 2021 17:48:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1625680094; bh=vvwMXjdpAOUVfaE6QIqNUFd4xufRLAI7AFwFrBKqC0g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=bABlUhNq8rfmkhrO4NWIKZqs7jmr3Rn8VQ9L/YIAnMZHRnQ1AkDX9bN5Rg3itU8TR 7Q03Ey8cAR8oXT4O4we6clJedusLIY0DCYFMRs9s6m0/FzTwPW9NB+IT36qnD+JKrr fk8RT0lnaDcAc7fccsU9Jup37Zssth6ruS9+kzOQBTQjWntHk/TrXb05dr7I3bV47A FhexIQDJUf62X9AIkesGfSx0W3gikXXrcveU+BmTkUCuzPGlqaSam5zrRnPwuOzokn 2Pg0B0imlp5RAYEuUORh4k03ki+4DRXf+e85/wlVCkU3L6Te86Qq6rKo3S/g8FS4WM Vb4NjpxV2SDsA== Date: Wed, 7 Jul 2021 10:48:12 -0700 From: Jaegeuk Kim To: Chao Yu Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 RFC] f2fs: fix to force keeping write barrier for strict fsync mode Message-ID: References: <20210601101024.119356-1-yuchao0@huawei.com> <648a96f7-2c83-e9ed-0cbd-4ee8e4797724@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/02, Chao Yu wrote: > On 2021/7/2 9:32, Jaegeuk Kim wrote: > > On 07/02, Chao Yu wrote: > > > On 2021/7/2 1:10, Jaegeuk Kim wrote: > > > > On 06/01, Chao Yu wrote: > > > > > [1] https://www.mail-archive.com/linux-f2fs-devel@lists.sourceforge.net/msg15126.html > > > > > > > > > > As [1] reported, if lower device doesn't support write barrier, in below > > > > > case: > > > > > > > > > > - write page #0; persist > > > > > - overwrite page #0 > > > > > - fsync > > > > > - write data page #0 OPU into device's cache > > > > > - write inode page into device's cache > > > > > - issue flush > > > > > > > > Well, we have preflush for node writes, so I don't think this is the case. > > > > > > > > fio.op_flags |= REQ_PREFLUSH | REQ_FUA; > > > > > > This is only used for atomic write case, right? > > > > > > I mean the common case which is called from f2fs_issue_flush() in > > > f2fs_do_sync_file(). > > > > How about adding PREFLUSH when writing node blocks aligned to the above set? > > You mean implementation like v1 as below? > > https://lore.kernel.org/linux-f2fs-devel/20200120100045.70210-1-yuchao0@huawei.com/ Yea, I think so. :P > > Thanks, > > > > > > > > > And please see do_checkpoint(), we call f2fs_flush_device_cache() and > > > commit_checkpoint() separately to keep persistence order of CP datas. > > > > > > See commit 46706d5917f4 ("f2fs: flush cp pack except cp pack 2 page at first") > > > for details. > > > > > > Thanks, > > > > > > > > > > > > > > > > > If SPO is triggered during flush command, inode page can be persisted > > > > > before data page #0, so that after recovery, inode page can be recovered > > > > > with new physical block address of data page #0, however there may > > > > > contains dummy data in new physical block address. > > > > > > > > > > Then what user will see is: after overwrite & fsync + SPO, old data in > > > > > file was corrupted, if any user do care about such case, we can suggest > > > > > user to use STRICT fsync mode, in this mode, we will force to trigger > > > > > preflush command to persist data in device cache in prior to node > > > > > writeback, it avoids potential data corruption during fsync(). > > > > > > > > > > Signed-off-by: Chao Yu > > > > > --- > > > > > v2: > > > > > - fix this by adding additional preflush command rather than using > > > > > atomic write flow. > > > > > fs/f2fs/file.c | 14 ++++++++++++++ > > > > > 1 file changed, 14 insertions(+) > > > > > > > > > > diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c > > > > > index 7d5311d54f63..238ca2a733ac 100644 > > > > > --- a/fs/f2fs/file.c > > > > > +++ b/fs/f2fs/file.c > > > > > @@ -301,6 +301,20 @@ static int f2fs_do_sync_file(struct file *file, loff_t start, loff_t end, > > > > > f2fs_exist_written_data(sbi, ino, UPDATE_INO)) > > > > > goto flush_out; > > > > > goto out; > > > > > + } else { > > > > > + /* > > > > > + * for OPU case, during fsync(), node can be persisted before > > > > > + * data when lower device doesn't support write barrier, result > > > > > + * in data corruption after SPO. > > > > > + * So for strict fsync mode, force to trigger preflush to keep > > > > > + * data/node write order to avoid potential data corruption. > > > > > + */ > > > > > + if (F2FS_OPTION(sbi).fsync_mode == FSYNC_MODE_STRICT && > > > > > + !atomic) { > > > > > + ret = f2fs_issue_flush(sbi, inode->i_ino); > > > > > + if (ret) > > > > > + goto out; > > > > > + } > > > > > } > > > > > go_write: > > > > > /* > > > > > -- > > > > > 2.29.2