From: "Martin K. Petersen (Oracle)" <mkp@kernel.org>
To: Laurence Oberman <loberman@redhat.com>
Cc: linux-scsi@vger.kernel.org,
"Martin K . Petersen" <mkp@kernel.org>,
"James E . J . Bottomley" <James.Bottomley@HansenPartnership.com>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
John Meneghini <jmeneghi@redhat.com>,
emilne@redhat.com, bgurney@redhat.com
Subject: Re: [PATCH v4 0/4] scsi: st: Restore drive settings and state after reset and MTLOAD
Date: Sat, 03 Oct 2026 10:36:04 -0400 [thread overview]
Message-ID: <yq14if2lulv.fsf@mail.kernel.org> (raw)
In-Reply-To: <20260929192821.997675-1-loberman@redhat.com>
Laurence,
> After a device reset st blocks tape access until one of MTREW, MTOFFL,
> MTLOAD, MTRETEN, MTERASE, MTSEEK or MTEOM clears the reset condition.
> Testing the reset handling on scsi_debug and on IBM LTO drives found that
> several settings and parts of the driver state do not survive the reset
> or an MTLOAD.
Applied to 7.4/scsi-staging, thanks!
--
Martin K. Petersen
prev parent reply other threads:[~2026-10-03 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 19:28 [PATCH v4 0/4] scsi: st: Restore drive settings and state after reset and MTLOAD Laurence Oberman
2026-09-29 19:28 ` [PATCH v4 1/4] scsi: st: Restore changed drive settings after reset also for MTLOAD and MTRETEN Laurence Oberman
2026-09-29 19:28 ` [PATCH v4 2/4] scsi: st: Record the tape position after a successful MTLOAD Laurence Oberman
2026-09-29 19:28 ` [PATCH v4 3/4] scsi: st: Restore the drive buffering mode after reset Laurence Oberman
2026-09-29 19:28 ` [PATCH v4 4/4] scsi: st: Relock the door after a reset Laurence Oberman
2026-09-30 15:58 ` [PATCH v4 0/4] scsi: st: Restore drive settings and state after reset and MTLOAD "Kai Mäkisara (Kolumbus)"
2026-10-03 14:36 ` Martin K. Petersen (Oracle) [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=yq14if2lulv.fsf@mail.kernel.org \
--to=mkp@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=bgurney@redhat.com \
--cc=emilne@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
/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.