Home
last modified time | relevance | path

Searched hist:f50f88b9 (Results 1 – 3 of 3) sorted by relevance

/qemu/block/
H A Dqcow2.hf50f88b9 Fri Dec 07 17:08:46 GMT 2012 Kevin Wolf <kwolf@redhat.com> qcow2: Allocate l2meta only for cluster allocations

Even for writes to already allocated clusters, an l2meta is allocated,
though it stays effectively unused. After this patch, only allocating
requests still have one. Each l2meta now describes an in-flight request
that writes to clusters that are not yet hooked up in the L2 table.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
H A Dqcow2-cluster.cf50f88b9 Fri Dec 07 17:08:46 GMT 2012 Kevin Wolf <kwolf@redhat.com> qcow2: Allocate l2meta only for cluster allocations

Even for writes to already allocated clusters, an l2meta is allocated,
though it stays effectively unused. After this patch, only allocating
requests still have one. Each l2meta now describes an in-flight request
that writes to clusters that are not yet hooked up in the L2 table.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
H A Dqcow2.c8d2497c3 Mon Jan 14 16:31:31 GMT 2013 Kevin Wolf <kwolf@redhat.com> qcow2: Fix segfault on zero-length write

One of the recent refactoring patches (commit f50f88b9) didn't take care
to initialise l2meta properly, so with zero-length writes, which don't
even enter the write loop, qemu just segfaulted.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
f50f88b9 Fri Dec 07 17:08:46 GMT 2012 Kevin Wolf <kwolf@redhat.com> qcow2: Allocate l2meta only for cluster allocations

Even for writes to already allocated clusters, an l2meta is allocated,
though it stays effectively unused. After this patch, only allocating
requests still have one. Each l2meta now describes an in-flight request
that writes to clusters that are not yet hooked up in the L2 table.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>