From: Daniel Paziyski <danielpaziyski@gmail.com>
To: Keith Busch <kbusch@kernel.org>, Klaus Jensen <its@irrelevant.dk>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Daniel Paziyski <danielpaziyski@gmail.com>,
qemu-stable@nongnu.org, Jesper Devantier <foss@defmacro.it>,
qemu-block@nongnu.org (open list:nvme),
qemu-devel@nongnu.org (open list:All patches CC here)
Subject: [PATCH 0/3] NVMe hotunplug and PCI SR-IOV fixes
Date: Wed, 5 Aug 2026 14:45:15 +0200 [thread overview]
Message-ID: <20260805124519.30054-1-danielpaziyski@gmail.com> (raw)
In this series, an assertion failure and a memory leak are fixed when unplugging
SR-IOV capable NVMe controllers.
The third patch fixes a null pointer dereference that occurs due to a mistake
in the SR-IOV capable device realization logic. I discovered it while testing
the code for these patches, so that's why I am including it in this series.
Cc: qemu-stable@nongnu.org
Daniel Paziyski (3):
hw/nvme: fix assertion failure on sr-iov capable nvme controller
removal
hw/nvme: fix memory leak on sr-iov capable nvme controller removal
pcie_sriov: register user created virtual function before realizing it
hw/nvme/ctrl.c | 12 ++++++++----
hw/pci/pci.c | 11 ++++++-----
hw/pci/pcie_sriov.c | 6 ------
3 files changed, 14 insertions(+), 15 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-05 13:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 12:45 Daniel Paziyski [this message]
2026-08-05 12:45 ` [PATCH 1/3] hw/nvme: fix assertion failure on sr-iov capable nvme controller removal Daniel Paziyski
2026-08-05 12:45 ` [PATCH 2/3] hw/nvme: fix memory leak " Daniel Paziyski
2026-08-05 12:45 ` [PATCH 3/3] pcie_sriov: register user created virtual function before realizing it Daniel Paziyski
2026-09-01 11:19 ` Michael S. Tsirkin
2026-09-01 13:24 ` Daniel Paziyski
2026-09-01 13:44 ` Michael S. Tsirkin
2026-09-01 15:37 ` Daniel Paziyski
2026-09-01 10:03 ` [PATCH 0/3] NVMe hotunplug and PCI SR-IOV fixes Daniel Paziyski
2026-09-05 12:35 ` Daniel Paziyski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260805124519.30054-1-danielpaziyski@gmail.com \
--to=danielpaziyski@gmail.com \
--cc=foss@defmacro.it \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.