From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Joshua Daley <jdaley@linux.ibm.com>, linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
mst@redhat.com, jasowang@redhat.com, pbonzini@redhat.com,
stefanha@redhat.com, eperezma@redhat.com,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com, farman@linux.ibm.com,
frankja@linux.ibm.com
Subject: Re: [PATCH v2 3/3] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init
Date: Mon, 16 Mar 2026 10:37:43 -0400 [thread overview]
Message-ID: <74fa682c-e07a-46a2-bd4e-c03ca6d906e6@linux.ibm.com> (raw)
In-Reply-To: <20260312174256.1557045-4-jdaley@linux.ibm.com>
On 3/12/26 1:42 PM, Joshua Daley wrote:
> The last step of virtscsi_handle_event is to call virtscsi_kick_event,
> which calls INIT_WORK on it's own work item. INIT_WORK resets the
> work item's data bits to 0.
>
> If this occurs while the work item is being flushed by
> cancel_work_sync, then kernel/workqueue.c/work_offqd_enable triggers a
> kernel warning, as it expects the "disable" bit to be 1:
>
> [ 21.450115] workqueue: work disable count underflowed
> [ 21.450117] WARNING: CPU: 1 PID: 56 at kernel/workqueue.c:4328 enable_work+0x10a/0x120
> ...
> [ 21.450171] Call Trace:
> [ 21.450173] [<000003db2e5bdc3e>] enable_work+0x10e/0x120
> [ 21.450176] ([<000003db2e5bdc3a>] enable_work+0x10a/0x120)
> [ 21.450178] [<000003db2e5bdd86>] cancel_work_sync+0x86/0xa0
> [ 21.450181] [<000003daae97d9e4>] virtscsi_remove+0xb4/0xd0 [virtio_scsi]
> [ 21.450184] [<000003db2ef3b5ca>] virtio_dev_remove+0x6a/0xd0
> [ 21.450186] [<000003db2ef9106c>] device_release_driver_internal+0x1ac/0x260
> [ 21.450190] [<000003db2ef8edc8>] bus_remove_device+0xf8/0x190
> [ 21.450192] [<000003db2ef88d72>] device_del+0x142/0x340
> [ 21.450194] [<000003db2ef88fa0>] device_unregister+0x30/0xa0
> [ 21.450196] [<000003db2ef3b2fa>] unregister_virtio_device+0x2a/0x40
>
> This warning may occur if a controller is detached immediately
> following a disk detach.
>
> Move the INIT_WORK call to prevent this. Don't re-init event list
> work items in virtscsi_kick_event, init them only once in
> virtscsi_init instead.
>
> Signed-off-by: Joshua Daley <jdaley@linux.ibm.com>
With patch 2 either squashed in OR moved after this one:
Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
next prev parent reply other threads:[~2026-03-16 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 17:42 [PATCH v2 0/3] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init Joshua Daley
2026-03-12 17:42 ` [PATCH v2 1/3] scsi: virtio_scsi: kick event_list unconditionally Joshua Daley
2026-03-16 14:37 ` Matthew Rosato
2026-03-12 17:42 ` [PATCH v2 2/3] scsi: virtio_scsi: remove unnecessary fn declaration Joshua Daley
2026-03-16 13:55 ` Matthew Rosato
2026-03-16 14:55 ` Joshua Daley
2026-03-12 17:42 ` [PATCH v2 3/3] scsi: virtio_scsi: move INIT_WORK calls to virtscsi_init Joshua Daley
2026-03-16 14:37 ` Matthew Rosato [this message]
2026-03-14 7:10 ` [PATCH v2 0/3] " 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=74fa682c-e07a-46a2-bd4e-c03ca6d906e6@linux.ibm.com \
--to=mjrosato@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=jdaley@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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