From: Joshua Daley <jdaley@linux.ibm.com>
To: linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
jdaley@linux.ibm.com, mst@redhat.com, jasowang@redhat.com,
pbonzini@redhat.com, stefanha@redhat.com, eperezma@redhat.com,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, mjrosato@linux.ibm.com,
farman@linux.ibm.com, frankja@linux.ibm.com
Subject: [PATCH 0/1] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init
Date: Thu, 26 Feb 2026 21:43:44 +0100 [thread overview]
Message-ID: <20260226204345.1904786-1-jdaley@linux.ibm.com> (raw)
This patch avoids a kernel warning that may occur if a virtio_scsi
controller is detached immediately following a disk detach. See the
commit message for details. The following are instructions to
produce the warning (without the proposed patch).
Timing matters--if all event work items call INIT_WORK before they are
flushed by cancel_work_sync, then the warning will not occur.
The warning will occur consistently if a sleep is added in
virtscsi_kick_event before the INIT_WORK call, like so:
#include <linux/delay.h>
static int virtscsi_kick_event(struct virtio_scsi *vscsi,
struct virtio_scsi_event_node *event_node)
{
int err;
struct scatterlist sg;
unsigned long flags;
-> msleep(1000);
INIT_WORK(&event_node->work, virtscsi_handle_event);
...
}
Then, just detach a disk and its controller in quick succession:
virsh detach-device --domain <domain> disk.xml; \
virsh detach-device --domain <domain> controller.xml
where disk.xml and controller.xml are text files containing the XML
of the disk and controller.
Or, with the libvirt python module:
domain.detachDevice(str(disk_xml))
domain.detachDevice(str(controller_xml))
Joshua Daley (1):
scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init
drivers/scsi/virtio_scsi.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2026-02-26 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 20:43 Joshua Daley [this message]
2026-02-26 20:43 ` [PATCH 1/1] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init Joshua Daley
2026-03-03 21:45 ` Eric Farman
2026-03-04 18:14 ` Joshua Daley
2026-03-09 3:06 ` Stefan Hajnoczi
2026-03-09 21:03 ` Joshua Daley
2026-03-09 23:07 ` Stefan Hajnoczi
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=20260226204345.1904786-1-jdaley@linux.ibm.com \
--to=jdaley@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=eperezma@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox