diff options
| author | Eric Blake <eblake@redhat.com> | 2016-05-06 10:26:27 -0600 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2016-05-12 15:22:08 +0200 |
| commit | 8341f00dc207b80a1b2e7c7784890c9b0446d062 (patch) | |
| tree | e2ff324dc93b8b03a5dff95e6fd576116591aad3 /block/crypto.c | |
| parent | 0e01b76e7cc43068f6b8cc05297f61539ccd5279 (diff) | |
| download | qemu-8341f00dc207b80a1b2e7c7784890c9b0446d062.tar.gz | |
block: Allow BDRV_REQ_FUA through blk_pwrite()
We have several block drivers that understand BDRV_REQ_FUA,
and emulate it in the block layer for the rest by a full flush.
But without a way to actually request BDRV_REQ_FUA during a
pass-through blk_pwrite(), FUA-aware block drivers like NBD are
forced to repeat the emulation logic of a full flush regardless
of whether the backend they are writing to could do it more
efficiently.
This patch just wires up a flags argument; followup patches
will actually make use of it in the NBD driver and in qemu-io.
Signed-off-by: Eric Blake <eblake@redhat.com>
Acked-by: Denis V. Lunev <den@openvz.org>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block/crypto.c')
| -rw-r--r-- | block/crypto.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/crypto.c b/block/crypto.c index 1903e84fbd..32ba17ce00 100644 --- a/block/crypto.c +++ b/block/crypto.c @@ -91,7 +91,7 @@ static ssize_t block_crypto_write_func(QCryptoBlock *block, struct BlockCryptoCreateData *data = opaque; ssize_t ret; - ret = blk_pwrite(data->blk, offset, buf, buflen); + ret = blk_pwrite(data->blk, offset, buf, buflen, 0); if (ret < 0) { error_setg_errno(errp, -ret, "Could not write encryption header"); return ret; |