linux-kernel - RE: [PATCH] exfat: do not clear VolumeDirty in writeback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <HK2PR04MB38913077A55A6E7124A41A4281049@HK2PR04MB3891.apcprd04.prod.outlook.com>
Date:   Thu, 3 Mar 2022 07:08:04 +0000
From:   "Yuezhang.Mo@...y.com" <Yuezhang.Mo@...y.com>
To:     "Kohada.Tetsuhiro@...MitsubishiElectric.co.jp" 
        <Kohada.Tetsuhiro@...MitsubishiElectric.co.jp>
CC:     "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linkinjeon@...nel.org" <linkinjeon@...nel.org>,
        "sj1557.seo@...sung.com" <sj1557.seo@...sung.com>
Subject: RE: [PATCH] exfat: do not clear VolumeDirty in writeback

Hi, Kohada.Tetsuhiro

> >(PS: The original logic is to clear VolumeDirty after BitMap, FAT and directory
> entries are updated.)
> 
> However, the writing order was not guaranteed.
> More synchronous writes are needed to guarantee the write order.

If "dirsync" or "sync" is enabled, BitMap, FAT and directory entries are guaranteed to be written in order.
This is the reason to keep clearing VolumeDirty.


Best Regards,
Yuezhang Mo