From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: linux-kernel@vger.kernel.org, Maxim Levitsky <mlevitsk@redhat.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"open list:SCSI SUBSYSTEM" <linux-scsi@vger.kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"open list:VIRTIO BLOCK AND SCSI DRIVERS"
<virtualization@lists.linux-foundation.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>
Subject: Re: [PATCH 0/1] virtio-scsi: fix missing unplug events when all LUNs are unplugged at the same time
Date: Wed, 29 Jul 2020 22:24:01 -0400 [thread overview]
Message-ID: <159607582923.27464.4409897545362766716.b4-ty@oracle.com> (raw)
In-Reply-To: <20200729194806.4933-1-mlevitsk@redhat.com>
On Wed, 29 Jul 2020 22:48:05 +0300, Maxim Levitsky wrote:
> virtio-scsi currently has limit of 8 outstanding notifications so when more that
> 8 LUNs are unplugged, some are missed.
>
> Commit 5ff843721467 ("scsi: virtio_scsi: unplug LUNs when events missed")
> Fixed this by checking the 'event overflow' bit and manually scanned the bus
> to see which LUNs are still there.
>
> [...]
Applied to 5.9/scsi-queue, thanks!
[1/1] scsi: virtio-scsi: Correctly handle the case where all LUNs are unplugged
https://git.kernel.org/mkp/scsi/c/b12149f2698c
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-07-30 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 19:48 [PATCH 0/1] virtio-scsi: fix missing unplug events when all LUNs are unplugged at the same time Maxim Levitsky
2020-07-29 19:48 ` [PATCH 1/1] scsi: virtio-scsi: handle correctly case when all LUNs were unplugged Maxim Levitsky
2020-07-29 22:10 ` Paolo Bonzini
2020-07-30 2:24 ` Martin K. Petersen [this message]
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=159607582923.27464.4409897545362766716.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=jasowang@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).