All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, pbonzini@redhat.com, gveitmic@redhat.com,
	bmarzins@redhat.com, fam@euphon.net, qemu-devel@nongnu.org
Subject: Re: [PATCH for-11.0] scsi: Don't consider LOGICAL UNIT NOT SUPPORTED guest recoverable
Date: Mon, 30 Mar 2026 14:18:42 -0400	[thread overview]
Message-ID: <20260330181842.GB179613@fedora> (raw)
In-Reply-To: <20260330121635.49205-1-kwolf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

On Mon, Mar 30, 2026 at 02:16:35PM +0200, Kevin Wolf wrote:
> When commit bdf9613b introduced scsi_sense_buf_is_guest_recoverable(),
> it included LOGICAL UNIT NOT SUPPORTED in the list of guest recoverable
> sense codes. It doesn't really explain how the codes to be in the list
> were selected.
> 
> As the LUN doesn't come from the guest, but from the block backend
> (usually the SCSI device on the host that was opened with host_device,
> but it could also be the iscsi block driver), there is really no way the
> guest could influence this.
> 
> It seems that on some storage arrays, LOGICAL UNIT NOT SUPPORTED can
> happen during failover operations. When combined with multipath, the
> request should be retried on another path instead of being reported to
> the guest, which would offline the filesystem in response.
> 
> Simply returning false in scsi_sense_buf_is_guest_recoverable() will
> enable the retry logic in file-posix, and will also make sure that if
> the error persists, the configured error policy is respected so that the
> VM can be stopped.
> 
> Buglink: https://redhat.atlassian.net/browse/RHEL-158212
> Fixes: bdf9613b7f87 ('scsi: explicitly list guest-recoverable sense codes')
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  scsi/utils.c | 1 -
>  1 file changed, 1 deletion(-)

Paolo: Are you taking this through your SCSI tree or would you like
Peter to merge it directly?

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2026-03-30 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 12:16 [PATCH for-11.0] scsi: Don't consider LOGICAL UNIT NOT SUPPORTED guest recoverable Kevin Wolf
2026-03-30 13:11 ` Paolo Bonzini
2026-03-30 18:18 ` Stefan Hajnoczi [this message]
2026-03-31 12:28   ` Kevin Wolf
2026-03-31 21:32 ` Michael Tokarev

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=20260330181842.GB179613@fedora \
    --to=stefanha@redhat.com \
    --cc=bmarzins@redhat.com \
    --cc=fam@euphon.net \
    --cc=gveitmic@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.