linux-kernel - Re: [PATCH] virtio_blk: support barriers without FLUSH feature

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

Date:	Wed, 16 Jun 2010 11:26:32 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Christoph Hellwig <hch@....de>
Cc:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] virtio_blk: support barriers without FLUSH feature

On Tue, 15 Jun 2010 10:13:48 pm Christoph Hellwig wrote:
> If we want to support barriers with the cache=writethrough mode in qemu
> we need to tell the block layer that we only need queue drains to
> implement a barrier.  Follow the model set by SCSI and IDE and assume
> that there is no volatile write cache if the host doesn't advertize it.
> While this might imply working barriers on old qemu versions or other
> hypervisors that actually have a volatile write cache this is only a
> cosmetic issue - these hypervisors don't guarantee any data integrity
> with or without this patch, but with the patch we at least provide
> data ordering.
> 
> Signed-off-by: Christoph Hellwig <hch@....de>

Thanks, applied.

Cheers,
Rusty.
--
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/