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: Fri, 14 Mar 2014 15:15:11 +0100 From: Jan Kara <jack@...e.cz> To: Tejun Heo <tj@...nel.org> Cc: Roman Peniaev <r.peniaev@...il.com>, 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 14-03-14 10:11:43, Tejun Heo wrote: > > Also, could you please help me do understand how can I guarantee > > integrity in case of block device with big volatile > > cache and filesystem, which does not support REQ_FLUSH/FUA? > > If a device has a volatile cache but doesn't support flush, it can't > guarantee integrity. There's no way for its user to determine or > force whether certain data is on non-volatile media. It's an > inherently broken device. I think his problem was that the device does support REQ_FLUSH/FUA but the filesystem on top of it doesn't issue it properly. That's a filesystem problem so fix the filesystem... :) Which one is it? Honza -- Jan Kara <jack@...e.cz> SUSE Labs, CR -- 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