[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <TYAPR01MB5353A452BE48880A1D4778B5900C9@TYAPR01MB5353.jpnprd01.prod.outlook.com>
Date: Fri, 11 Mar 2022 04:34:42 +0000
From: "Kohada.Tetsuhiro@...MitsubishiElectric.co.jp"
<Kohada.Tetsuhiro@...MitsubishiElectric.co.jp>
To: "Yuezhang.Mo@...y.com" <Yuezhang.Mo@...y.com>,
Namjae Jeon <linkinjeon@...nel.org>,
"sj1557.seo@...sung.com" <sj1557.seo@...sung.com>
CC: "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Andy.Wu@...y.com" <Andy.Wu@...y.com>,
"Wataru.Aoyama@...y.com" <Wataru.Aoyama@...y.com>
Subject: Re: [PATCH v2] exfat: do not clear VolumeDirty in writeback
Hi, Yuezhang,Mo
I think it's good.
It will not be possible to clear dirty automatically, but I think device life and reliable integrity are more important.
> - if (sync)
> - sync_dirty_buffer(sbi->boot_bh);
> + sync_dirty_buffer(sbi->boot_bh);
> +
Use __sync_dirty_buffer() with REQ_FUA/REQ_PREFLUSH instead to guarantee a strict write order (including devices).
BR
T .Kohada
Powered by blists - more mailing lists