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
| ||
|
Date: Tue, 15 Mar 2022 08:20:08 +0900 From: Namjae Jeon <linkinjeon@...nel.org> To: "Kohada.Tetsuhiro@...MitsubishiElectric.co.jp" <Kohada.Tetsuhiro@...mitsubishielectric.co.jp>, "Yuezhang.Mo@...y.com" <Yuezhang.Mo@...y.com> Cc: "sj1557.seo@...sung.com" <sj1557.seo@...sung.com>, "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 2022-03-11 13:34 GMT+09:00, Kohada.Tetsuhiro@...MitsubishiElectric.co.jp <Kohada.Tetsuhiro@...mitsubishielectric.co.jp>: > 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). Yuezhang, It seems to make sense. Can you check this ? Thanks! > > BR > T .Kohada
Powered by blists - more mailing lists