blkdev_issue_flush really issues a WRITE_BARRIER -- is that okay?

[Jeff Moyer]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/