From: "Ewan D. Milne" <emilne@redhat.com>
To: linux-scsi@vger.kernel.org
Subject: [PATCH 0/2] Fix SCSI async abort handling when eh_deadline is active
Date: Mon, 25 Oct 2021 10:39:50 -0400 [thread overview]
Message-ID: <20211025143952.17128-1-emilne@redhat.com> (raw)
There is a code path in the SCSI async abort handling that can cause error
handling of subsequent scsi_cmnds to proceed immediately to host reset with no
other attempt at recovery.
This can be seen by the following:
modprobe scsi_debug every_nth=10 opts=4
echo 7 > /sys/module/scsi_mod/parameters/scsi_logging_level
echo 10 > /sys/devices/pseudo_0/adapter0/host8/scsi_host/host<N>/eh_deadline
and performing I/O to the scsi_debug device, the host will get reset immediately
when prior aborts succeeded, because ->last_reset does not get invalidated.
The patch series contains a fix, followed by a simplification
of the control flow to remove duplicate code. Only the first patch
is Cc: stable as the second part doesn't qualify. Yes, I know the
first patch is >100 lines, I couldn't make it smaller unfortunately.
Signed-off-by: Ewan D. Milne <emilne@redhat.com>
Ewan D. Milne (2):
scsi: core: avoid leaving shost->last_reset with stale value if EH
does not run
scsi: core: simplify control flow in scmd_eh_abort_handler
drivers/scsi/hosts.c | 1 +
drivers/scsi/scsi_error.c | 92 ++++++++++++++++++++++++++++++-----------------
drivers/scsi/scsi_lib.c | 1 +
include/scsi/scsi_cmnd.h | 2 +-
include/scsi/scsi_host.h | 1 +
5 files changed, 63 insertions(+), 34 deletions(-)
--
2.1.0
next reply other threads:[~2021-10-25 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 14:39 Ewan D. Milne [this message]
2021-10-25 14:39 ` [PATCH 1/2] scsi: core: avoid leaving shost->last_reset with stale value if EH does not run Ewan D. Milne
2021-10-28 3:29 ` Martin K. Petersen
2021-10-28 20:44 ` Ewan D. Milne
2021-10-25 14:39 ` [PATCH 2/2] scsi: core: simplify control flow in scmd_eh_abort_handler Ewan D. Milne
2021-10-28 3:31 ` Martin K. Petersen
2021-10-28 20:45 ` Ewan D. Milne
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=20211025143952.17128-1-emilne@redhat.com \
--to=emilne@redhat.com \
--cc=linux-scsi@vger.kernel.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