| 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
| ||
|
Message-ID: <CACZ9PQWGwhYK6PTQ6wJ2tumzxcy4n3ws_VPLjAFBA5OM2ce6-g@mail.gmail.com> Date: Fri, 14 Mar 2014 23:29:59 +0900 From: Roman Peniaev <r.peniaev@...il.com> To: Tejun Heo <tj@...nel.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Jan Kara <jack@...e.cz>, Alexander Viro <viro@...iv.linux.org.uk>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk> Subject: Re: [PATCH 1/1] fs/mpage.c: forgotten WRITE_SYNC in case of data integrity write On Fri, Mar 14, 2014 at 11:20 PM, Tejun Heo <tj@...nel.org> wrote: > On Fri, Mar 14, 2014 at 11:17:56PM +0900, Roman Peniaev wrote: >> No, no. Not device does not support flush, filesystem does not care about flush. >> (take any old school, e.g. ext2) >> >> We did some write, and then we did fsync. >> But filesystem does not support REQ_FLUSH/FUA so block device will never >> get the checkpoint where it should really flush everything. >> >> So, fsync will not guarantee any integrity in that case. > > Oh, no idea. Fix the filesystem to support REQ_FLUSH? :) Yep, best variant. But I was thinking that there should be some guarantees from fsync (and friends) calls, which will issue flush after completion of every writeback request. But no way > > -- > tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists