linux-kernel - blkdev_issue_flush really issues a WRITE

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-next>] [day] [month] [year] [list]

Message-ID: <x49hbu4semq.fsf@segfault.boston.devel.redhat.com>
Date:	Mon, 12 Oct 2009 13:31:25 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Linux Kernel Mailing <linux-kernel@...r.kernel.org>
Cc:	Jens Axboe <jens.axboe@...cle.com>
Subject: blkdev_issue_flush really issues a WRITE_BARRIER -- is that okay?

Hi,

While looking though Christoph's patch to call blkdev_issue_flush for
fsync on block devices, I noticed that it only issues a WRITE_BARRIER.
I don't see how that guarantees that data is on stable storage.  Am I
missing something?  Shouldn't this translate to a FLUSH CACHE or
SYNCHRONIZE CACHE command?

My apologies if this has been discussed before.

Thanks!
Jeff
--
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/