On 8/9/23 06:39, Klaus Jensen wrote:
From: Klaus Jensen
Hi,
The following changes since commit a8fc5165aab02f328ccd148aafec1e59fd1426eb:
Merge tag 'nvme-next-pull-request' ofhttps://gitlab.com/birkelund/qemu into
staging (2023-08-08 16:39:20 -0700)
are available in the Git repository at:
From: Klaus Jensen
The Reclaim Unit Update operation in I/O Management Receive does not
verify the presence of a configured endurance group prior to accessing
it.
Fix this.
Cc: qemu-sta...@nongnu.org
Fixes: 73064edfb864 ("hw/nvme: flexible data placement emulation")
Reviewed-by: Jesper Wendel D
From: Klaus Jensen
nvme_directive_receive() does not check if an endurance group has been
configured (set) prior to testing if flexible data placement is enabled
or not.
Fix this.
Cc: qemu-sta...@nongnu.org
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/1815
Fixes: 73064edfb864 ("hw/nv
From: Klaus Jensen
Hi,
The following changes since commit a8fc5165aab02f328ccd148aafec1e59fd1426eb:
Merge tag 'nvme-next-pull-request' of https://gitlab.com/birkelund/qemu into
staging (2023-08-08 16:39:20 -0700)
are available in the Git repository at:
https://gitlab.com/birkelund/qemu.g
On Tue, Aug 08, 2023 at 05:16:12PM +0200, Klaus Jensen wrote:
> From: Klaus Jensen
>
> Fix two potential accesses to null pointers.
>
> Klaus Jensen (2):
> hw/nvme: fix null pointer access in directive receive
> hw/nvme: fix null pointer access in ruh update
>
> hw/nvme/ctrl.c | 10 +++
On 8/8/23 19:08, Stefan Hajnoczi wrote:
> On Mon, Jul 31, 2023 at 05:33:38PM -0300, Fabiano Rosas wrote:
>> We can fail the blk_insert_bs() at init_blk_migration(), leaving the
>> BlkMigDevState without a dirty_bitmap and BlockDriverState. Account
>> for the possibly missing elements when doing cle