diff options
author | Martin K. Petersen <martin.petersen@oracle.com> | 2024-11-06 21:19:06 -0500 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2024-11-06 21:19:06 -0500 |
commit | 128faa1845a2d5b0178b986f3bd18fb38cc08cc2 (patch) | |
tree | a437153ffdec395fdcd026f23e5e35e3467d3582 /rust/helpers/workqueue.c | |
parent | 007cd6ba9aace998acab29a3b9e9b1ce02f91f5d (diff) | |
parent | a4550b28c8c853e7241ecf30b4f1d9c6bc631fda (diff) | |
download | linux-128faa1845a2d5b0178b986f3bd18fb38cc08cc2.tar.gz linux-128faa1845a2d5b0178b986f3bd18fb38cc08cc2.tar.bz2 linux-128faa1845a2d5b0178b986f3bd18fb38cc08cc2.zip |
Merge patch series "scsi: st: Device reset patches"
Kai Mäkisara <Kai.Makisara@kolumbus.fi> says:
These three patches were developed in response to Bugzilla report
https://bugzilla.kernel.org/show_bug.cgi?id=219419
After device reset, the tape driver allows only operations that don't
write or read anything from tape. The reason for this is that many
(most ?) drives rewind the tape after reset and the subsequent reads
or writes would not be at the tape location the user expects. Reading
and writing is allowed again when the user does something to position the
tape (e.g., rewind).
The Bugzilla report considers the case when a user, after reset, tries
to read the drive status with MTIOCGET ioctl, but it fails. MTIOCGET
does not return much useful data after reset, but it can be allowed.
MTLOAD positions the tape and it should be allowed. The second patch
adds these to the set of allowed operations after device reset.
The first patch fixes a bug seen when developing the second patch.
V2: The third patch is added to fix a bug that resulted in not
blocking writes if reset occurs while the device file is not open.
Link: https://lore.kernel.org/r/20241106095723.63254-1-Kai.Makisara@kolumbus.fi
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'rust/helpers/workqueue.c')
0 files changed, 0 insertions, 0 deletions