Linux virtualization list
 help / color / mirror / Atom feed
From: Mike Christie <michael.christie@oracle.com>
To: physicalmtea@gmail.com, mst@redhat.com
Cc: jasowangio@gmail.com, pbonzini@redhat.com, stefanha@redhat.com,
	eperezma@redhat.com, nab@linux-iscsi.org, asias@redhat.com,
	virtualization@lists.linux.dev, kvm@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] vhost-scsi: preserve event ordering
Date: Tue, 15 Sep 2026 16:00:55 -0500	[thread overview]
Message-ID: <c8867400-9b31-49b4-b74a-3d27e6046330@oracle.com> (raw)
In-Reply-To: <20260915094244.7900-2-physicalmtea@gmail.com>

On 9/15/26 4:42 AM, physicalmtea@gmail.com wrote:
> diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c
> index 7a1f39a32..37f681aab 100644
> --- a/drivers/vhost/scsi.c
> +++ b/drivers/vhost/scsi.c
> @@ -637,7 +637,7 @@ static void vhost_scsi_complete_events(struct vhost_scsi *vs, bool drop)
>   	struct llist_node *llnode;
>   
>   	mutex_lock(&vq->mutex);
> -	llnode = llist_del_all(&vs->vs_event_list);
> +	llnode = llist_reverse_order(llist_del_all(&vs->vs_event_list));
>   	llist_for_each_entry_safe(evt, t, llnode, list) {
>   		if (!drop)
>   			vhost_scsi_do_evt_work(vs, evt);
> -- 
> 2.34.1
> 
> 

Reviewed-by: Mike Christie <michael.christie@oracle.com>


  parent reply	other threads:[~2026-09-15 21:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15  9:42 [PATCH 0/2] vhost-scsi: preserve event ordering and fix fallback deadlock physicalmtea
2026-09-15  9:42 ` [PATCH 1/2] vhost-scsi: preserve event ordering physicalmtea
2026-09-15  9:51   ` sashiko-bot
2026-09-15 21:00   ` Mike Christie [this message]
2026-09-15  9:42 ` [PATCH 2/2] vhost-scsi: do not relock event vq mutex on send_evt fallback physicalmtea
2026-09-15  9:52   ` sashiko-bot

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=c8867400-9b31-49b4-b74a-3d27e6046330@oracle.com \
    --to=michael.christie@oracle.com \
    --cc=asias@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowangio@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=netdev@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=physicalmtea@gmail.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