block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/*
|
|
|
|
* Block driver for Hyper-V VHDX Images
|
|
|
|
*
|
|
|
|
* Copyright (c) 2013 Red Hat, Inc.,
|
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Jeff Cody <jcody@redhat.com>
|
|
|
|
*
|
|
|
|
* This is based on the "VHDX Format Specification v1.00", published 8/25/2012
|
|
|
|
* by Microsoft:
|
|
|
|
* https://www.microsoft.com/en-us/download/details.aspx?id=34750
|
|
|
|
*
|
|
|
|
* This file covers the functionality of the metadata log writing, parsing, and
|
|
|
|
* replay.
|
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU LGPL, version 2 or later.
|
|
|
|
* See the COPYING.LIB file in the top-level directory.
|
|
|
|
*
|
|
|
|
*/
|
2019-05-23 16:35:07 +02:00
|
|
|
|
2016-01-18 19:01:42 +01:00
|
|
|
#include "qemu/osdep.h"
|
include/qemu/osdep.h: Don't include qapi/error.h
Commit 57cb38b included qapi/error.h into qemu/osdep.h to get the
Error typedef. Since then, we've moved to include qemu/osdep.h
everywhere. Its file comment explains: "To avoid getting into
possible circular include dependencies, this file should not include
any other QEMU headers, with the exceptions of config-host.h,
compiler.h, os-posix.h and os-win32.h, all of which are doing a
similar job to this file and are under similar constraints."
qapi/error.h doesn't do a similar job, and it doesn't adhere to
similar constraints: it includes qapi-types.h. That's in excess of
100KiB of crap most .c files don't actually need.
Add the typedef to qemu/typedefs.h, and include that instead of
qapi/error.h. Include qapi/error.h in .c files that need it and don't
get it now. Include qapi-types.h in qom/object.h for uint16List.
Update scripts/clean-includes accordingly. Update it further to match
reality: replace config.h by config-target.h, add sysemu/os-posix.h,
sysemu/os-win32.h. Update the list of includes in the qemu/osdep.h
comment quoted above similarly.
This reduces the number of objects depending on qapi/error.h from "all
of them" to less than a third. Unfortunately, the number depending on
qapi-types.h shrinks only a little. More work is needed for that one.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
[Fix compilation without the spice devel packages. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-03-14 09:01:28 +01:00
|
|
|
#include "qapi/error.h"
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
#include "block/block_int.h"
|
2015-03-17 18:29:20 +01:00
|
|
|
#include "qemu/error-report.h"
|
2016-03-15 17:22:36 +01:00
|
|
|
#include "qemu/bswap.h"
|
2022-02-26 19:07:23 +01:00
|
|
|
#include "qemu/memalign.h"
|
2018-05-03 21:50:20 +02:00
|
|
|
#include "vhdx.h"
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
|
|
|
|
|
|
|
|
typedef struct VHDXLogSequence {
|
|
|
|
bool valid;
|
|
|
|
uint32_t count;
|
|
|
|
VHDXLogEntries log;
|
|
|
|
VHDXLogEntryHeader hdr;
|
|
|
|
} VHDXLogSequence;
|
|
|
|
|
|
|
|
typedef struct VHDXLogDescEntries {
|
|
|
|
VHDXLogEntryHeader hdr;
|
|
|
|
VHDXLogDescriptor desc[];
|
|
|
|
} VHDXLogDescEntries;
|
|
|
|
|
|
|
|
static const MSGUID zero_guid = { 0 };
|
|
|
|
|
|
|
|
/* The log located on the disk is circular buffer containing
|
|
|
|
* sectors of 4096 bytes each.
|
|
|
|
*
|
|
|
|
* It is assumed for the read/write functions below that the
|
|
|
|
* circular buffer scheme uses a 'one sector open' to indicate
|
|
|
|
* the buffer is full. Given the validation methods used for each
|
|
|
|
* sector, this method should be compatible with other methods that
|
|
|
|
* do not waste a sector.
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
|
|
/* Allow peeking at the hdr entry at the beginning of the current
|
|
|
|
* read index, without advancing the read index */
|
|
|
|
static int vhdx_log_peek_hdr(BlockDriverState *bs, VHDXLogEntries *log,
|
|
|
|
VHDXLogEntryHeader *hdr)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
uint64_t offset;
|
|
|
|
uint32_t read;
|
|
|
|
|
|
|
|
assert(hdr != NULL);
|
|
|
|
|
|
|
|
/* peek is only supported on sector boundaries */
|
|
|
|
if (log->read % VHDX_LOG_SECTOR_SIZE) {
|
|
|
|
ret = -EFAULT;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
read = log->read;
|
|
|
|
/* we are guaranteed that a) log sectors are 4096 bytes,
|
|
|
|
* and b) the log length is a multiple of 1MB. So, there
|
|
|
|
* is always a round number of sectors in the buffer */
|
|
|
|
if ((read + sizeof(VHDXLogEntryHeader)) > log->length) {
|
|
|
|
read = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (read == log->write) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
offset = log->offset + read;
|
|
|
|
|
block: Change bdrv_{pread,pwrite,pwrite_sync}() param order
Swap 'buf' and 'bytes' around for consistency with
bdrv_co_{pread,pwrite}(), and in preparation to implement these
functions using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pread(child, offset, buf, bytes, flags)
+ bdrv_pread(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite(child, offset, buf, bytes, flags)
+ bdrv_pwrite(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite_sync(child, offset, buf, bytes, flags)
+ bdrv_pwrite_sync(child, offset, bytes, buf, flags)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-3-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:36 +02:00
|
|
|
ret = bdrv_pread(bs->file, offset, sizeof(VHDXLogEntryHeader), hdr, 0);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
2014-08-06 21:54:58 +02:00
|
|
|
vhdx_log_entry_hdr_le_import(hdr);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Index increment for log, based on sector boundaries */
|
|
|
|
static int vhdx_log_inc_idx(uint32_t idx, uint64_t length)
|
|
|
|
{
|
|
|
|
idx += VHDX_LOG_SECTOR_SIZE;
|
|
|
|
/* we are guaranteed that a) log sectors are 4096 bytes,
|
|
|
|
* and b) the log length is a multiple of 1MB. So, there
|
|
|
|
* is always a round number of sectors in the buffer */
|
|
|
|
return idx >= length ? 0 : idx;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Reset the log to empty */
|
|
|
|
static void vhdx_log_reset(BlockDriverState *bs, BDRVVHDXState *s)
|
|
|
|
{
|
|
|
|
MSGUID guid = { 0 };
|
|
|
|
s->log.read = s->log.write = 0;
|
|
|
|
/* a log guid of 0 indicates an empty log to any parser of v0
|
|
|
|
* VHDX logs */
|
|
|
|
vhdx_update_headers(bs, s, false, &guid);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Reads num_sectors from the log (all log sectors are 4096 bytes),
|
|
|
|
* into buffer 'buffer'. Upon return, *sectors_read will contain
|
|
|
|
* the number of sectors successfully read.
|
|
|
|
*
|
|
|
|
* It is assumed that 'buffer' is already allocated, and of sufficient
|
|
|
|
* size (i.e. >= 4096*num_sectors).
|
|
|
|
*
|
|
|
|
* If 'peek' is true, then the tail (read) pointer for the circular buffer is
|
|
|
|
* not modified.
|
|
|
|
*
|
|
|
|
* 0 is returned on success, -errno otherwise. */
|
|
|
|
static int vhdx_log_read_sectors(BlockDriverState *bs, VHDXLogEntries *log,
|
|
|
|
uint32_t *sectors_read, void *buffer,
|
|
|
|
uint32_t num_sectors, bool peek)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
uint64_t offset;
|
|
|
|
uint32_t read;
|
|
|
|
|
|
|
|
read = log->read;
|
|
|
|
|
|
|
|
*sectors_read = 0;
|
|
|
|
while (num_sectors) {
|
|
|
|
if (read == log->write) {
|
|
|
|
/* empty */
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
offset = log->offset + read;
|
|
|
|
|
block: Change bdrv_{pread,pwrite,pwrite_sync}() param order
Swap 'buf' and 'bytes' around for consistency with
bdrv_co_{pread,pwrite}(), and in preparation to implement these
functions using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pread(child, offset, buf, bytes, flags)
+ bdrv_pread(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite(child, offset, buf, bytes, flags)
+ bdrv_pwrite(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite_sync(child, offset, buf, bytes, flags)
+ bdrv_pwrite_sync(child, offset, bytes, buf, flags)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-3-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:36 +02:00
|
|
|
ret = bdrv_pread(bs->file, offset, VHDX_LOG_SECTOR_SIZE, buffer, 0);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
read = vhdx_log_inc_idx(read, log->length);
|
|
|
|
|
|
|
|
*sectors_read = *sectors_read + 1;
|
|
|
|
num_sectors--;
|
|
|
|
}
|
|
|
|
|
|
|
|
exit:
|
|
|
|
if (!peek) {
|
|
|
|
log->read = read;
|
|
|
|
}
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2013-10-30 15:44:47 +01:00
|
|
|
/* Writes num_sectors to the log (all log sectors are 4096 bytes),
|
|
|
|
* from buffer 'buffer'. Upon return, *sectors_written will contain
|
|
|
|
* the number of sectors successfully written.
|
|
|
|
*
|
|
|
|
* It is assumed that 'buffer' is at least 4096*num_sectors large.
|
|
|
|
*
|
|
|
|
* 0 is returned on success, -errno otherwise */
|
|
|
|
static int vhdx_log_write_sectors(BlockDriverState *bs, VHDXLogEntries *log,
|
|
|
|
uint32_t *sectors_written, void *buffer,
|
|
|
|
uint32_t num_sectors)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
uint64_t offset;
|
|
|
|
uint32_t write;
|
|
|
|
void *buffer_tmp;
|
|
|
|
BDRVVHDXState *s = bs->opaque;
|
|
|
|
|
|
|
|
ret = vhdx_user_visible_write(bs, s);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
write = log->write;
|
|
|
|
|
|
|
|
buffer_tmp = buffer;
|
|
|
|
while (num_sectors) {
|
|
|
|
|
|
|
|
offset = log->offset + write;
|
|
|
|
write = vhdx_log_inc_idx(write, log->length);
|
|
|
|
if (write == log->read) {
|
|
|
|
/* full */
|
|
|
|
break;
|
|
|
|
}
|
block: Change bdrv_{pread,pwrite,pwrite_sync}() param order
Swap 'buf' and 'bytes' around for consistency with
bdrv_co_{pread,pwrite}(), and in preparation to implement these
functions using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pread(child, offset, buf, bytes, flags)
+ bdrv_pread(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite(child, offset, buf, bytes, flags)
+ bdrv_pwrite(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite_sync(child, offset, buf, bytes, flags)
+ bdrv_pwrite_sync(child, offset, bytes, buf, flags)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-3-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:36 +02:00
|
|
|
ret = bdrv_pwrite(bs->file, offset, VHDX_LOG_SECTOR_SIZE, buffer_tmp,
|
block: Add a 'flags' param to bdrv_{pread,pwrite,pwrite_sync}()
For consistency with other I/O functions, and in preparation to
implement them using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes; @@
- bdrv_pread(child, offset, buf, bytes)
+ bdrv_pread(child, offset, buf, bytes, 0)
@@ expression child, offset, buf, bytes; @@
- bdrv_pwrite(child, offset, buf, bytes)
+ bdrv_pwrite(child, offset, buf, bytes, 0)
@@ expression child, offset, buf, bytes; @@
- bdrv_pwrite_sync(child, offset, buf, bytes)
+ bdrv_pwrite_sync(child, offset, buf, bytes, 0)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-2-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:35 +02:00
|
|
|
0);
|
2013-10-30 15:44:47 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
buffer_tmp += VHDX_LOG_SECTOR_SIZE;
|
|
|
|
|
|
|
|
log->write = write;
|
|
|
|
*sectors_written = *sectors_written + 1;
|
|
|
|
num_sectors--;
|
|
|
|
}
|
|
|
|
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* Validates a log entry header */
|
|
|
|
static bool vhdx_log_hdr_is_valid(VHDXLogEntries *log, VHDXLogEntryHeader *hdr,
|
|
|
|
BDRVVHDXState *s)
|
|
|
|
{
|
|
|
|
int valid = false;
|
|
|
|
|
2014-08-06 21:54:58 +02:00
|
|
|
if (hdr->signature != VHDX_LOG_SIGNATURE) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* if the individual entry length is larger than the whole log
|
|
|
|
* buffer, that is obviously invalid */
|
|
|
|
if (log->length < hdr->entry_length) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* length of entire entry must be in units of 4KB (log sector size) */
|
|
|
|
if (hdr->entry_length % (VHDX_LOG_SECTOR_SIZE)) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* per spec, sequence # must be > 0 */
|
|
|
|
if (hdr->sequence_number == 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* log entries are only valid if they match the file-wide log guid
|
|
|
|
* found in the active header */
|
|
|
|
if (!guid_eq(hdr->log_guid, s->headers[s->curr_header]->log_guid)) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (hdr->descriptor_count * sizeof(VHDXLogDescriptor) > hdr->entry_length) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
valid = true;
|
|
|
|
|
|
|
|
exit:
|
|
|
|
return valid;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Given a log header, this will validate that the descriptors and the
|
|
|
|
* corresponding data sectors (if applicable)
|
|
|
|
*
|
|
|
|
* Validation consists of:
|
|
|
|
* 1. Making sure the sequence numbers matches the entry header
|
|
|
|
* 2. Verifying a valid signature ('zero' or 'desc' for descriptors)
|
|
|
|
* 3. File offset field is a multiple of 4KB
|
|
|
|
* 4. If a data descriptor, the corresponding data sector
|
|
|
|
* has its signature ('data') and matching sequence number
|
|
|
|
*
|
|
|
|
* @desc: the data buffer containing the descriptor
|
|
|
|
* @hdr: the log entry header
|
|
|
|
*
|
|
|
|
* Returns true if valid
|
|
|
|
*/
|
|
|
|
static bool vhdx_log_desc_is_valid(VHDXLogDescriptor *desc,
|
|
|
|
VHDXLogEntryHeader *hdr)
|
|
|
|
{
|
|
|
|
bool ret = false;
|
|
|
|
|
|
|
|
if (desc->sequence_number != hdr->sequence_number) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
if (desc->file_offset % VHDX_LOG_SECTOR_SIZE) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
2014-08-06 21:54:58 +02:00
|
|
|
if (desc->signature == VHDX_LOG_ZERO_SIGNATURE) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (desc->zero_length % VHDX_LOG_SECTOR_SIZE == 0) {
|
|
|
|
/* valid */
|
|
|
|
ret = true;
|
|
|
|
}
|
2014-08-06 21:54:58 +02:00
|
|
|
} else if (desc->signature == VHDX_LOG_DESC_SIGNATURE) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* valid */
|
|
|
|
ret = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Prior to sector data for a log entry, there is the header
|
|
|
|
* and the descriptors referenced in the header:
|
|
|
|
*
|
|
|
|
* [] = 4KB sector
|
|
|
|
*
|
|
|
|
* [ hdr, desc ][ desc ][ ... ][ data ][ ... ]
|
|
|
|
*
|
|
|
|
* The first sector in a log entry has a 64 byte header, and
|
|
|
|
* up to 126 32-byte descriptors. If more descriptors than
|
|
|
|
* 126 are required, then subsequent sectors can have up to 128
|
|
|
|
* descriptors. Each sector is 4KB. Data follows the descriptor
|
|
|
|
* sectors.
|
|
|
|
*
|
|
|
|
* This will return the number of sectors needed to encompass
|
|
|
|
* the passed number of descriptors in desc_cnt.
|
|
|
|
*
|
|
|
|
* This will never return 0, even if desc_cnt is 0.
|
|
|
|
*/
|
|
|
|
static int vhdx_compute_desc_sectors(uint32_t desc_cnt)
|
|
|
|
{
|
|
|
|
uint32_t desc_sectors;
|
|
|
|
|
|
|
|
desc_cnt += 2; /* account for header in first sector */
|
|
|
|
desc_sectors = desc_cnt / 128;
|
|
|
|
if (desc_cnt % 128) {
|
|
|
|
desc_sectors++;
|
|
|
|
}
|
|
|
|
|
|
|
|
return desc_sectors;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Reads the log header, and subsequent descriptors (if any). This
|
|
|
|
* will allocate all the space for buffer, which must be NULL when
|
|
|
|
* passed into this function. Each descriptor will also be validated,
|
|
|
|
* and error returned if any are invalid. */
|
|
|
|
static int vhdx_log_read_desc(BlockDriverState *bs, BDRVVHDXState *s,
|
2014-08-06 21:54:58 +02:00
|
|
|
VHDXLogEntries *log, VHDXLogDescEntries **buffer,
|
|
|
|
bool convert_endian)
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
uint32_t desc_sectors;
|
|
|
|
uint32_t sectors_read;
|
|
|
|
VHDXLogEntryHeader hdr;
|
|
|
|
VHDXLogDescEntries *desc_entries = NULL;
|
2014-08-06 21:54:58 +02:00
|
|
|
VHDXLogDescriptor desc;
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
int i;
|
|
|
|
|
|
|
|
assert(*buffer == NULL);
|
|
|
|
|
|
|
|
ret = vhdx_log_peek_hdr(bs, log, &hdr);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
2014-08-06 21:54:58 +02:00
|
|
|
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (vhdx_log_hdr_is_valid(log, &hdr, s) == false) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
desc_sectors = vhdx_compute_desc_sectors(hdr.descriptor_count);
|
2015-06-16 14:19:22 +02:00
|
|
|
desc_entries = qemu_try_blockalign(bs->file->bs,
|
2014-05-20 13:55:50 +02:00
|
|
|
desc_sectors * VHDX_LOG_SECTOR_SIZE);
|
|
|
|
if (desc_entries == NULL) {
|
|
|
|
ret = -ENOMEM;
|
|
|
|
goto exit;
|
|
|
|
}
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
|
|
|
|
ret = vhdx_log_read_sectors(bs, log, §ors_read, desc_entries,
|
|
|
|
desc_sectors, false);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto free_and_exit;
|
|
|
|
}
|
|
|
|
if (sectors_read != desc_sectors) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto free_and_exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* put in proper endianness, and validate each desc */
|
|
|
|
for (i = 0; i < hdr.descriptor_count; i++) {
|
2014-08-06 21:54:58 +02:00
|
|
|
desc = desc_entries->desc[i];
|
|
|
|
vhdx_log_desc_le_import(&desc);
|
|
|
|
if (convert_endian) {
|
|
|
|
desc_entries->desc[i] = desc;
|
|
|
|
}
|
|
|
|
if (vhdx_log_desc_is_valid(&desc, &hdr) == false) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
ret = -EINVAL;
|
|
|
|
goto free_and_exit;
|
|
|
|
}
|
|
|
|
}
|
2014-08-06 21:54:58 +02:00
|
|
|
if (convert_endian) {
|
|
|
|
desc_entries->hdr = hdr;
|
|
|
|
}
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
|
|
|
|
*buffer = desc_entries;
|
|
|
|
goto exit;
|
|
|
|
|
|
|
|
free_and_exit:
|
|
|
|
qemu_vfree(desc_entries);
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* Flushes the descriptor described by desc to the VHDX image file.
|
|
|
|
* If the descriptor is a data descriptor, than 'data' must be non-NULL,
|
|
|
|
* and >= 4096 bytes (VHDX_LOG_SECTOR_SIZE), containing the data to be
|
|
|
|
* written.
|
|
|
|
*
|
|
|
|
* Verification is performed to make sure the sequence numbers of a data
|
|
|
|
* descriptor match the sequence number in the desc.
|
|
|
|
*
|
|
|
|
* For a zero descriptor, it may describe multiple sectors to fill with zeroes.
|
|
|
|
* In this case, it should be noted that zeroes are written to disk, and the
|
|
|
|
* image file is not extended as a sparse file. */
|
|
|
|
static int vhdx_log_flush_desc(BlockDriverState *bs, VHDXLogDescriptor *desc,
|
|
|
|
VHDXLogDataSector *data)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
uint64_t seq, file_offset;
|
|
|
|
uint32_t offset = 0;
|
|
|
|
void *buffer = NULL;
|
|
|
|
uint64_t count = 1;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
buffer = qemu_blockalign(bs, VHDX_LOG_SECTOR_SIZE);
|
|
|
|
|
2014-08-06 21:54:58 +02:00
|
|
|
if (desc->signature == VHDX_LOG_DESC_SIGNATURE) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* data sector */
|
|
|
|
if (data == NULL) {
|
|
|
|
ret = -EFAULT;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* The sequence number of the data sector must match that
|
|
|
|
* in the descriptor */
|
|
|
|
seq = data->sequence_high;
|
|
|
|
seq <<= 32;
|
|
|
|
seq |= data->sequence_low & 0xffffffff;
|
|
|
|
|
|
|
|
if (seq != desc->sequence_number) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Each data sector is in total 4096 bytes, however the first
|
|
|
|
* 8 bytes, and last 4 bytes, are located in the descriptor */
|
|
|
|
memcpy(buffer, &desc->leading_bytes, 8);
|
|
|
|
offset += 8;
|
|
|
|
|
|
|
|
memcpy(buffer+offset, data->data, 4084);
|
|
|
|
offset += 4084;
|
|
|
|
|
|
|
|
memcpy(buffer+offset, &desc->trailing_bytes, 4);
|
|
|
|
|
2014-08-06 21:54:58 +02:00
|
|
|
} else if (desc->signature == VHDX_LOG_ZERO_SIGNATURE) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* write 'count' sectors of sector */
|
|
|
|
memset(buffer, 0, VHDX_LOG_SECTOR_SIZE);
|
|
|
|
count = desc->zero_length / VHDX_LOG_SECTOR_SIZE;
|
2014-08-06 21:54:57 +02:00
|
|
|
} else {
|
|
|
|
error_report("Invalid VHDX log descriptor entry signature 0x%" PRIx32,
|
|
|
|
desc->signature);
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
file_offset = desc->file_offset;
|
|
|
|
|
|
|
|
/* count is only > 1 if we are writing zeroes */
|
|
|
|
for (i = 0; i < count; i++) {
|
block: Change bdrv_{pread,pwrite,pwrite_sync}() param order
Swap 'buf' and 'bytes' around for consistency with
bdrv_co_{pread,pwrite}(), and in preparation to implement these
functions using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pread(child, offset, buf, bytes, flags)
+ bdrv_pread(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite(child, offset, buf, bytes, flags)
+ bdrv_pwrite(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite_sync(child, offset, buf, bytes, flags)
+ bdrv_pwrite_sync(child, offset, bytes, buf, flags)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-3-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:36 +02:00
|
|
|
ret = bdrv_pwrite_sync(bs->file, file_offset, VHDX_LOG_SECTOR_SIZE,
|
|
|
|
buffer, 0);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
file_offset += VHDX_LOG_SECTOR_SIZE;
|
|
|
|
}
|
|
|
|
|
|
|
|
exit:
|
|
|
|
qemu_vfree(buffer);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Flush the entire log (as described by 'logs') to the VHDX image
|
|
|
|
* file, and then set the log to 'empty' status once complete.
|
|
|
|
*
|
|
|
|
* The log entries should be validate prior to flushing */
|
|
|
|
static int vhdx_log_flush(BlockDriverState *bs, BDRVVHDXState *s,
|
|
|
|
VHDXLogSequence *logs)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
int i;
|
|
|
|
uint32_t cnt, sectors_read;
|
|
|
|
uint64_t new_file_size;
|
|
|
|
void *data = NULL;
|
2017-08-07 14:38:19 +02:00
|
|
|
int64_t file_length;
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
VHDXLogDescEntries *desc_entries = NULL;
|
|
|
|
VHDXLogEntryHeader hdr_tmp = { 0 };
|
|
|
|
|
|
|
|
cnt = logs->count;
|
|
|
|
|
|
|
|
data = qemu_blockalign(bs, VHDX_LOG_SECTOR_SIZE);
|
|
|
|
|
|
|
|
ret = vhdx_user_visible_write(bs, s);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* each iteration represents one log sequence, which may span multiple
|
|
|
|
* sectors */
|
|
|
|
while (cnt--) {
|
|
|
|
ret = vhdx_log_peek_hdr(bs, &logs->log, &hdr_tmp);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
2017-08-07 14:38:19 +02:00
|
|
|
file_length = bdrv_getlength(bs->file->bs);
|
|
|
|
if (file_length < 0) {
|
|
|
|
ret = file_length;
|
|
|
|
goto exit;
|
|
|
|
}
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* if the log shows a FlushedFileOffset larger than our current file
|
|
|
|
* size, then that means the file has been truncated / corrupted, and
|
|
|
|
* we must refused to open it / use it */
|
2017-08-07 14:38:19 +02:00
|
|
|
if (hdr_tmp.flushed_file_offset > file_length) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
2014-08-06 21:54:58 +02:00
|
|
|
ret = vhdx_log_read_desc(bs, s, &logs->log, &desc_entries, true);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
for (i = 0; i < desc_entries->hdr.descriptor_count; i++) {
|
2014-08-06 21:54:58 +02:00
|
|
|
if (desc_entries->desc[i].signature == VHDX_LOG_DESC_SIGNATURE) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* data sector, so read a sector to flush */
|
|
|
|
ret = vhdx_log_read_sectors(bs, &logs->log, §ors_read,
|
|
|
|
data, 1, false);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
if (sectors_read != 1) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
2014-08-06 21:54:58 +02:00
|
|
|
vhdx_log_data_le_import(data);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
ret = vhdx_log_flush_desc(bs, &desc_entries->desc[i], data);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
}
|
2017-08-07 14:38:19 +02:00
|
|
|
if (file_length < desc_entries->hdr.last_file_offset) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
new_file_size = desc_entries->hdr.last_file_offset;
|
2019-03-27 10:56:34 +01:00
|
|
|
if (new_file_size % (1 * MiB)) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* round up to nearest 1MB boundary */
|
2017-08-07 14:38:20 +02:00
|
|
|
new_file_size = QEMU_ALIGN_UP(new_file_size, MiB);
|
|
|
|
if (new_file_size > INT64_MAX) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
2019-09-18 11:51:40 +02:00
|
|
|
ret = bdrv_truncate(bs->file, new_file_size, false,
|
2020-04-24 14:54:40 +02:00
|
|
|
PREALLOC_MODE_OFF, 0, NULL);
|
2017-08-07 14:38:22 +02:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
qemu_vfree(desc_entries);
|
|
|
|
desc_entries = NULL;
|
|
|
|
}
|
|
|
|
|
2017-08-07 14:38:21 +02:00
|
|
|
ret = bdrv_flush(bs);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* once the log is fully flushed, indicate that we have an empty log
|
|
|
|
* now. This also sets the log guid to 0, to indicate an empty log */
|
|
|
|
vhdx_log_reset(bs, s);
|
|
|
|
|
|
|
|
exit:
|
|
|
|
qemu_vfree(data);
|
|
|
|
qemu_vfree(desc_entries);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int vhdx_validate_log_entry(BlockDriverState *bs, BDRVVHDXState *s,
|
|
|
|
VHDXLogEntries *log, uint64_t seq,
|
|
|
|
bool *valid, VHDXLogEntryHeader *entry)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
VHDXLogEntryHeader hdr;
|
|
|
|
void *buffer = NULL;
|
|
|
|
uint32_t i, desc_sectors, total_sectors, crc;
|
|
|
|
uint32_t sectors_read = 0;
|
|
|
|
VHDXLogDescEntries *desc_buffer = NULL;
|
|
|
|
|
|
|
|
*valid = false;
|
|
|
|
|
|
|
|
ret = vhdx_log_peek_hdr(bs, log, &hdr);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto inc_and_exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (vhdx_log_hdr_is_valid(log, &hdr, s) == false) {
|
|
|
|
goto inc_and_exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (seq > 0) {
|
|
|
|
if (hdr.sequence_number != seq + 1) {
|
|
|
|
goto inc_and_exit;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
desc_sectors = vhdx_compute_desc_sectors(hdr.descriptor_count);
|
|
|
|
|
2014-08-06 21:54:58 +02:00
|
|
|
/* Read all log sectors, and calculate log checksum */
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
|
|
|
|
total_sectors = hdr.entry_length / VHDX_LOG_SECTOR_SIZE;
|
|
|
|
|
|
|
|
|
2014-03-24 09:30:17 +01:00
|
|
|
/* read_desc() will increment the read idx */
|
2014-08-06 21:54:58 +02:00
|
|
|
ret = vhdx_log_read_desc(bs, s, log, &desc_buffer, false);
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto free_and_exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
crc = vhdx_checksum_calc(0xffffffff, (void *)desc_buffer,
|
|
|
|
desc_sectors * VHDX_LOG_SECTOR_SIZE, 4);
|
|
|
|
crc ^= 0xffffffff;
|
|
|
|
|
|
|
|
buffer = qemu_blockalign(bs, VHDX_LOG_SECTOR_SIZE);
|
|
|
|
if (total_sectors > desc_sectors) {
|
|
|
|
for (i = 0; i < total_sectors - desc_sectors; i++) {
|
|
|
|
sectors_read = 0;
|
|
|
|
ret = vhdx_log_read_sectors(bs, log, §ors_read, buffer,
|
|
|
|
1, false);
|
|
|
|
if (ret < 0 || sectors_read != 1) {
|
|
|
|
goto free_and_exit;
|
|
|
|
}
|
|
|
|
crc = vhdx_checksum_calc(crc, buffer, VHDX_LOG_SECTOR_SIZE, -1);
|
|
|
|
crc ^= 0xffffffff;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
crc ^= 0xffffffff;
|
2014-08-06 21:54:58 +02:00
|
|
|
if (crc != hdr.checksum) {
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
goto free_and_exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
*valid = true;
|
|
|
|
*entry = hdr;
|
|
|
|
goto free_and_exit;
|
|
|
|
|
|
|
|
inc_and_exit:
|
|
|
|
log->read = vhdx_log_inc_idx(log->read, log->length);
|
|
|
|
|
|
|
|
free_and_exit:
|
|
|
|
qemu_vfree(buffer);
|
|
|
|
qemu_vfree(desc_buffer);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Search through the log circular buffer, and find the valid, active
|
|
|
|
* log sequence, if any exists
|
|
|
|
* */
|
|
|
|
static int vhdx_log_search(BlockDriverState *bs, BDRVVHDXState *s,
|
|
|
|
VHDXLogSequence *logs)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
uint32_t tail;
|
|
|
|
bool seq_valid = false;
|
|
|
|
VHDXLogSequence candidate = { 0 };
|
|
|
|
VHDXLogEntryHeader hdr = { 0 };
|
|
|
|
VHDXLogEntries curr_log;
|
|
|
|
|
|
|
|
memcpy(&curr_log, &s->log, sizeof(VHDXLogEntries));
|
|
|
|
curr_log.write = curr_log.length; /* assume log is full */
|
|
|
|
curr_log.read = 0;
|
|
|
|
|
|
|
|
|
|
|
|
/* now we will go through the whole log sector by sector, until
|
|
|
|
* we find a valid, active log sequence, or reach the end of the
|
|
|
|
* log buffer */
|
|
|
|
for (;;) {
|
|
|
|
uint64_t curr_seq = 0;
|
|
|
|
VHDXLogSequence current = { 0 };
|
|
|
|
|
|
|
|
tail = curr_log.read;
|
|
|
|
|
|
|
|
ret = vhdx_validate_log_entry(bs, s, &curr_log, curr_seq,
|
|
|
|
&seq_valid, &hdr);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (seq_valid) {
|
|
|
|
current.valid = true;
|
|
|
|
current.log = curr_log;
|
|
|
|
current.log.read = tail;
|
|
|
|
current.log.write = curr_log.read;
|
|
|
|
current.count = 1;
|
|
|
|
current.hdr = hdr;
|
|
|
|
|
|
|
|
|
|
|
|
for (;;) {
|
|
|
|
ret = vhdx_validate_log_entry(bs, s, &curr_log, curr_seq,
|
|
|
|
&seq_valid, &hdr);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
if (seq_valid == false) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
current.log.write = curr_log.read;
|
|
|
|
current.count++;
|
|
|
|
|
|
|
|
curr_seq = hdr.sequence_number;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (current.valid) {
|
|
|
|
if (candidate.valid == false ||
|
|
|
|
current.hdr.sequence_number > candidate.hdr.sequence_number) {
|
|
|
|
candidate = current;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (curr_log.read < tail) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
*logs = candidate;
|
|
|
|
|
|
|
|
if (candidate.valid) {
|
|
|
|
/* this is the next sequence number, for writes */
|
|
|
|
s->log.sequence = candidate.hdr.sequence_number + 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Parse the replay log. Per the VHDX spec, if the log is present
|
|
|
|
* it must be replayed prior to opening the file, even read-only.
|
|
|
|
*
|
|
|
|
* If read-only, we must replay the log in RAM (or refuse to open
|
|
|
|
* a dirty VHDX file read-only) */
|
2013-12-17 11:33:37 +01:00
|
|
|
int vhdx_parse_log(BlockDriverState *bs, BDRVVHDXState *s, bool *flushed,
|
|
|
|
Error **errp)
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
VHDXHeader *hdr;
|
|
|
|
VHDXLogSequence logs = { 0 };
|
|
|
|
|
|
|
|
hdr = s->headers[s->curr_header];
|
|
|
|
|
|
|
|
*flushed = false;
|
|
|
|
|
|
|
|
/* s->log.hdr is freed in vhdx_close() */
|
|
|
|
if (s->log.hdr == NULL) {
|
|
|
|
s->log.hdr = qemu_blockalign(bs, sizeof(VHDXLogEntryHeader));
|
|
|
|
}
|
|
|
|
|
|
|
|
s->log.offset = hdr->log_offset;
|
|
|
|
s->log.length = hdr->log_length;
|
|
|
|
|
|
|
|
if (s->log.offset < VHDX_LOG_MIN_SIZE ||
|
|
|
|
s->log.offset % VHDX_LOG_MIN_SIZE) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* per spec, only log version of 0 is supported */
|
|
|
|
if (hdr->log_version != 0) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If either the log guid, or log length is zero,
|
|
|
|
* then a replay log is not present */
|
|
|
|
if (guid_eq(hdr->log_guid, zero_guid)) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (hdr->log_length == 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (hdr->log_length % VHDX_LOG_MIN_SIZE) {
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
/* The log is present, we need to find if and where there is an active
|
|
|
|
* sequence of valid entries present in the log. */
|
|
|
|
|
|
|
|
ret = vhdx_log_search(bs, s, &logs);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (logs.valid) {
|
2021-05-27 17:40:54 +02:00
|
|
|
if (bdrv_is_read_only(bs)) {
|
block: Use bdrv_refresh_filename() to pull
Before this patch, bdrv_refresh_filename() is used in a pushing manner:
Whenever the BDS graph is modified, the parents of the modified edges
are supposed to be updated (recursively upwards). However, that is
nonviable, considering that we want child changes not to concern
parents.
Also, in the long run we want a pull model anyway: Here, we would have a
bdrv_filename() function which returns a BDS's filename, freshly
constructed.
This patch is an intermediate step. It adds bdrv_refresh_filename()
calls before every place a BDS.filename value is used. The only
exceptions are protocol drivers that use their own filename, which
clearly would not profit from refreshing that filename before.
Also, bdrv_get_encrypted_filename() is removed along the way (as a user
of BDS.filename), since it is completely unused.
In turn, all of the calls to bdrv_refresh_filename() before this patch
are removed, because we no longer have to call this function on graph
changes.
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-id: 20190201192935.18394-2-mreitz@redhat.com
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Max Reitz <mreitz@redhat.com>
2019-02-01 20:29:05 +01:00
|
|
|
bdrv_refresh_filename(bs);
|
2013-12-17 11:33:37 +01:00
|
|
|
ret = -EPERM;
|
2015-12-18 16:35:23 +01:00
|
|
|
error_setg(errp,
|
|
|
|
"VHDX image file '%s' opened read-only, but "
|
|
|
|
"contains a log that needs to be replayed",
|
|
|
|
bs->filename);
|
|
|
|
error_append_hint(errp, "To replay the log, run:\n"
|
|
|
|
"qemu-img check -r all '%s'\n",
|
|
|
|
bs->filename);
|
2013-12-17 11:33:37 +01:00
|
|
|
goto exit;
|
|
|
|
}
|
block: vhdx - log parsing, replay, and flush support
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search through an existing log, to find any valid
sequence of entries.
* Log replay and flush - replay an existing log, and flush/clear
the log when complete.
The VHDX log is a circular buffer, with elements (sectors) of 4KB.
A log entry is a variably-length number of sectors, that is
comprised of a header and 'descriptors', that describe each sector.
A log may contain multiple entries, know as a log sequence. In a log
sequence, each log entry immediately follows the previous entry, with an
incrementing sequence number. There can only ever be one active and
valid sequence in the log.
Each log entry must match the file log GUID in order to be valid (along
with other criteria). Once we have flushed all valid log entries, we
marked the file log GUID to be zero, which indicates a buffer with no
valid entries.
Signed-off-by: Jeff Cody <jcody@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-10-30 15:44:45 +01:00
|
|
|
/* now flush the log */
|
|
|
|
ret = vhdx_log_flush(bs, s, &logs);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
*flushed = true;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2013-10-30 15:44:47 +01:00
|
|
|
|
|
|
|
static void vhdx_log_raw_to_le_sector(VHDXLogDescriptor *desc,
|
|
|
|
VHDXLogDataSector *sector, void *data,
|
|
|
|
uint64_t seq)
|
|
|
|
{
|
|
|
|
/* 8 + 4084 + 4 = 4096, 1 log sector */
|
|
|
|
memcpy(&desc->leading_bytes, data, 8);
|
|
|
|
data += 8;
|
2018-10-16 19:09:38 +02:00
|
|
|
desc->leading_bytes = cpu_to_le64(desc->leading_bytes);
|
2013-10-30 15:44:47 +01:00
|
|
|
memcpy(sector->data, data, 4084);
|
|
|
|
data += 4084;
|
|
|
|
memcpy(&desc->trailing_bytes, data, 4);
|
2018-10-16 19:09:38 +02:00
|
|
|
desc->trailing_bytes = cpu_to_le32(desc->trailing_bytes);
|
2013-10-30 15:44:47 +01:00
|
|
|
data += 4;
|
|
|
|
|
|
|
|
sector->sequence_high = (uint32_t) (seq >> 32);
|
|
|
|
sector->sequence_low = (uint32_t) (seq & 0xffffffff);
|
|
|
|
sector->data_signature = VHDX_LOG_DATA_SIGNATURE;
|
|
|
|
|
|
|
|
vhdx_log_desc_le_export(desc);
|
|
|
|
vhdx_log_data_le_export(sector);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static int vhdx_log_write(BlockDriverState *bs, BDRVVHDXState *s,
|
|
|
|
void *data, uint32_t length, uint64_t offset)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
void *buffer = NULL;
|
|
|
|
void *merged_sector = NULL;
|
|
|
|
void *data_tmp, *sector_write;
|
|
|
|
unsigned int i;
|
|
|
|
int sector_offset;
|
|
|
|
uint32_t desc_sectors, sectors, total_length;
|
|
|
|
uint32_t sectors_written = 0;
|
|
|
|
uint32_t aligned_length;
|
|
|
|
uint32_t leading_length = 0;
|
|
|
|
uint32_t trailing_length = 0;
|
|
|
|
uint32_t partial_sectors = 0;
|
|
|
|
uint32_t bytes_written = 0;
|
|
|
|
uint64_t file_offset;
|
2017-08-07 14:38:19 +02:00
|
|
|
int64_t file_length;
|
2013-10-30 15:44:47 +01:00
|
|
|
VHDXHeader *header;
|
|
|
|
VHDXLogEntryHeader new_hdr;
|
|
|
|
VHDXLogDescriptor *new_desc = NULL;
|
|
|
|
VHDXLogDataSector *data_sector = NULL;
|
|
|
|
MSGUID new_guid = { 0 };
|
|
|
|
|
|
|
|
header = s->headers[s->curr_header];
|
|
|
|
|
|
|
|
/* need to have offset read data, and be on 4096 byte boundary */
|
|
|
|
|
|
|
|
if (length > header->log_length) {
|
|
|
|
/* no log present. we could create a log here instead of failing */
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (guid_eq(header->log_guid, zero_guid)) {
|
|
|
|
vhdx_guid_generate(&new_guid);
|
|
|
|
vhdx_update_headers(bs, s, false, &new_guid);
|
|
|
|
} else {
|
|
|
|
/* currently, we require that the log be flushed after
|
|
|
|
* every write. */
|
|
|
|
ret = -ENOTSUP;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* 0 is an invalid sequence number, but may also represent the first
|
|
|
|
* log write (or a wrapped seq) */
|
|
|
|
if (s->log.sequence == 0) {
|
|
|
|
s->log.sequence = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
sector_offset = offset % VHDX_LOG_SECTOR_SIZE;
|
2017-06-22 13:04:16 +02:00
|
|
|
file_offset = QEMU_ALIGN_DOWN(offset, VHDX_LOG_SECTOR_SIZE);
|
2013-10-30 15:44:47 +01:00
|
|
|
|
|
|
|
aligned_length = length;
|
|
|
|
|
|
|
|
/* add in the unaligned head and tail bytes */
|
|
|
|
if (sector_offset) {
|
|
|
|
leading_length = (VHDX_LOG_SECTOR_SIZE - sector_offset);
|
|
|
|
leading_length = leading_length > length ? length : leading_length;
|
|
|
|
aligned_length -= leading_length;
|
|
|
|
partial_sectors++;
|
|
|
|
}
|
|
|
|
|
|
|
|
sectors = aligned_length / VHDX_LOG_SECTOR_SIZE;
|
|
|
|
trailing_length = aligned_length - (sectors * VHDX_LOG_SECTOR_SIZE);
|
|
|
|
if (trailing_length) {
|
|
|
|
partial_sectors++;
|
|
|
|
}
|
|
|
|
|
|
|
|
sectors += partial_sectors;
|
|
|
|
|
2017-08-07 14:38:19 +02:00
|
|
|
file_length = bdrv_getlength(bs->file->bs);
|
|
|
|
if (file_length < 0) {
|
|
|
|
ret = file_length;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
2013-10-30 15:44:47 +01:00
|
|
|
/* sectors is now how many sectors the data itself takes, not
|
|
|
|
* including the header and descriptor metadata */
|
|
|
|
|
|
|
|
new_hdr = (VHDXLogEntryHeader) {
|
|
|
|
.signature = VHDX_LOG_SIGNATURE,
|
|
|
|
.tail = s->log.tail,
|
|
|
|
.sequence_number = s->log.sequence,
|
|
|
|
.descriptor_count = sectors,
|
|
|
|
.reserved = 0,
|
2017-08-07 14:38:19 +02:00
|
|
|
.flushed_file_offset = file_length,
|
|
|
|
.last_file_offset = file_length,
|
|
|
|
.log_guid = header->log_guid,
|
2013-10-30 15:44:47 +01:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
desc_sectors = vhdx_compute_desc_sectors(new_hdr.descriptor_count);
|
|
|
|
|
|
|
|
total_length = (desc_sectors + sectors) * VHDX_LOG_SECTOR_SIZE;
|
|
|
|
new_hdr.entry_length = total_length;
|
|
|
|
|
|
|
|
vhdx_log_entry_hdr_le_export(&new_hdr);
|
|
|
|
|
|
|
|
buffer = qemu_blockalign(bs, total_length);
|
|
|
|
memcpy(buffer, &new_hdr, sizeof(new_hdr));
|
|
|
|
|
2014-08-19 10:31:11 +02:00
|
|
|
new_desc = buffer + sizeof(new_hdr);
|
2013-10-30 15:44:47 +01:00
|
|
|
data_sector = buffer + (desc_sectors * VHDX_LOG_SECTOR_SIZE);
|
|
|
|
data_tmp = data;
|
|
|
|
|
|
|
|
/* All log sectors are 4KB, so for any partial sectors we must
|
|
|
|
* merge the data with preexisting data from the final file
|
|
|
|
* destination */
|
|
|
|
merged_sector = qemu_blockalign(bs, VHDX_LOG_SECTOR_SIZE);
|
|
|
|
|
|
|
|
for (i = 0; i < sectors; i++) {
|
|
|
|
new_desc->signature = VHDX_LOG_DESC_SIGNATURE;
|
|
|
|
new_desc->sequence_number = s->log.sequence;
|
|
|
|
new_desc->file_offset = file_offset;
|
|
|
|
|
|
|
|
if (i == 0 && leading_length) {
|
|
|
|
/* partial sector at the front of the buffer */
|
block: Change bdrv_{pread,pwrite,pwrite_sync}() param order
Swap 'buf' and 'bytes' around for consistency with
bdrv_co_{pread,pwrite}(), and in preparation to implement these
functions using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pread(child, offset, buf, bytes, flags)
+ bdrv_pread(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite(child, offset, buf, bytes, flags)
+ bdrv_pwrite(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite_sync(child, offset, buf, bytes, flags)
+ bdrv_pwrite_sync(child, offset, bytes, buf, flags)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-3-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:36 +02:00
|
|
|
ret = bdrv_pread(bs->file, file_offset, VHDX_LOG_SECTOR_SIZE,
|
|
|
|
merged_sector, 0);
|
2013-10-30 15:44:47 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
memcpy(merged_sector + sector_offset, data_tmp, leading_length);
|
|
|
|
bytes_written = leading_length;
|
|
|
|
sector_write = merged_sector;
|
|
|
|
} else if (i == sectors - 1 && trailing_length) {
|
|
|
|
/* partial sector at the end of the buffer */
|
block: Add a 'flags' param to bdrv_{pread,pwrite,pwrite_sync}()
For consistency with other I/O functions, and in preparation to
implement them using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes; @@
- bdrv_pread(child, offset, buf, bytes)
+ bdrv_pread(child, offset, buf, bytes, 0)
@@ expression child, offset, buf, bytes; @@
- bdrv_pwrite(child, offset, buf, bytes)
+ bdrv_pwrite(child, offset, buf, bytes, 0)
@@ expression child, offset, buf, bytes; @@
- bdrv_pwrite_sync(child, offset, buf, bytes)
+ bdrv_pwrite_sync(child, offset, buf, bytes, 0)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-2-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:35 +02:00
|
|
|
ret = bdrv_pread(bs->file, file_offset,
|
block: Change bdrv_{pread,pwrite,pwrite_sync}() param order
Swap 'buf' and 'bytes' around for consistency with
bdrv_co_{pread,pwrite}(), and in preparation to implement these
functions using generated_co_wrapper.
Callers were updated using this Coccinelle script:
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pread(child, offset, buf, bytes, flags)
+ bdrv_pread(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite(child, offset, buf, bytes, flags)
+ bdrv_pwrite(child, offset, bytes, buf, flags)
@@ expression child, offset, buf, bytes, flags; @@
- bdrv_pwrite_sync(child, offset, buf, bytes, flags)
+ bdrv_pwrite_sync(child, offset, bytes, buf, flags)
Resulting overly-long lines were then fixed by hand.
Signed-off-by: Alberto Faria <afaria@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Message-Id: <20220609152744.3891847-3-afaria@redhat.com>
Reviewed-by: Hanna Reitz <hreitz@redhat.com>
Signed-off-by: Hanna Reitz <hreitz@redhat.com>
2022-06-09 17:27:36 +02:00
|
|
|
VHDX_LOG_SECTOR_SIZE - trailing_length,
|
|
|
|
merged_sector + trailing_length, 0);
|
2013-10-30 15:44:47 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
memcpy(merged_sector, data_tmp, trailing_length);
|
|
|
|
bytes_written = trailing_length;
|
|
|
|
sector_write = merged_sector;
|
|
|
|
} else {
|
|
|
|
bytes_written = VHDX_LOG_SECTOR_SIZE;
|
|
|
|
sector_write = data_tmp;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* populate the raw sector data into the proper structures,
|
|
|
|
* as well as update the descriptor, and convert to proper
|
|
|
|
* endianness */
|
|
|
|
vhdx_log_raw_to_le_sector(new_desc, data_sector, sector_write,
|
|
|
|
s->log.sequence);
|
|
|
|
|
|
|
|
data_tmp += bytes_written;
|
|
|
|
data_sector++;
|
|
|
|
new_desc++;
|
|
|
|
file_offset += VHDX_LOG_SECTOR_SIZE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* checksum covers entire entry, from the log header through the
|
|
|
|
* last data sector */
|
|
|
|
vhdx_update_checksum(buffer, total_length,
|
|
|
|
offsetof(VHDXLogEntryHeader, checksum));
|
|
|
|
|
|
|
|
/* now write to the log */
|
2014-01-29 18:05:08 +01:00
|
|
|
ret = vhdx_log_write_sectors(bs, &s->log, §ors_written, buffer,
|
|
|
|
desc_sectors + sectors);
|
2013-10-30 15:44:47 +01:00
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (sectors_written != desc_sectors + sectors) {
|
|
|
|
/* instead of failing, we could flush the log here */
|
|
|
|
ret = -EINVAL;
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
s->log.sequence++;
|
|
|
|
/* write new tail */
|
|
|
|
s->log.tail = s->log.write;
|
|
|
|
|
|
|
|
exit:
|
|
|
|
qemu_vfree(buffer);
|
|
|
|
qemu_vfree(merged_sector);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Perform a log write, and then immediately flush the entire log */
|
|
|
|
int vhdx_log_write_and_flush(BlockDriverState *bs, BDRVVHDXState *s,
|
|
|
|
void *data, uint32_t length, uint64_t offset)
|
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
VHDXLogSequence logs = { .valid = true,
|
|
|
|
.count = 1,
|
|
|
|
.hdr = { 0 } };
|
|
|
|
|
|
|
|
|
|
|
|
/* Make sure data written (new and/or changed blocks) is stable
|
|
|
|
* on disk, before creating log entry */
|
2017-08-07 14:38:21 +02:00
|
|
|
ret = bdrv_flush(bs);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
2013-10-30 15:44:47 +01:00
|
|
|
ret = vhdx_log_write(bs, s, data, length, offset);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
logs.log = s->log;
|
|
|
|
|
|
|
|
/* Make sure log is stable on disk */
|
2017-08-07 14:38:21 +02:00
|
|
|
ret = bdrv_flush(bs);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
2013-10-30 15:44:47 +01:00
|
|
|
ret = vhdx_log_flush(bs, s, &logs);
|
|
|
|
if (ret < 0) {
|
|
|
|
goto exit;
|
|
|
|
}
|
|
|
|
|
|
|
|
s->log = logs.log;
|
|
|
|
|
|
|
|
exit:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|