From: Stefan Hajnoczi <stefanha@redhat.com>
To: Mike Christie <michael.christie@oracle.com>
Cc: jasowang@redhat.com, mst@redhat.com, sgarzare@redhat.com,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vhost-scsi: Fix log flooding with target does not exist errors
Date: Mon, 9 Jun 2025 09:48:22 -0400 [thread overview]
Message-ID: <20250609134822.GB29452@fedora> (raw)
In-Reply-To: <20250607171815.111030-1-michael.christie@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Sat, Jun 07, 2025 at 12:18:15PM -0500, Mike Christie wrote:
> As part of the normal initiator side scanning the guest's scsi layer
> will loop over all possible targets and send an inquiry. Since the
> max number of targets for virtio-scsi is 256, this results in 255
> error messages about targets not existing. When there's more than 1
> vhost-scsi device, then you get N * 255 log messages.
>
> It looks like the log message was added by accident in:
>
> commit 09d7583294aa ("vhost/scsi: Use common handling code in request
> queue handler")
>
> The patch was just making some coce common but added the vq_err call
> and I'm guessing the patch author forgot to enable the vq_err call
> (vq_err is implemented by pr_debug which defaults to off). So this
> patch removes the call since it's expected to hit this path during
> device discovery.
>
> Fixes: 09d7583294aa ("vhost/scsi: Use common handling code in request queue handler")
> Signed-off-by: Mike Christie <michael.christie@oracle.com>
> ---
> drivers/vhost/scsi.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-09 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-07 17:18 [PATCH] vhost-scsi: Fix log flooding with target does not exist errors Mike Christie
2025-06-09 13:48 ` Stefan Hajnoczi [this message]
2025-06-10 14:18 ` Stefano Garzarella
2025-06-10 16:30 ` michael.christie
2025-06-11 7:50 ` Stefano Garzarella
2025-06-11 20:57 ` Mike Christie
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=20250609134822.GB29452@fedora \
--to=stefanha@redhat.com \
--cc=jasowang@redhat.com \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=sgarzare@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