diff options
| author | Martin K. Petersen <martin.petersen@oracle.com> | 2019-05-20 17:57:18 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-31 16:43:09 +0300 |
| commit | 204d535040fad5192086852650e9ccfd449087f4 (patch) | |
| tree | 26854f412f3c6dc33529ed51fb482b2e5dd7177a /crypto/hmac.c | |
| parent | 15e5e4b9ff861952765cce30d1ed78bf22869ff8 (diff) | |
| download | linux-204d535040fad5192086852650e9ccfd449087f4.tar.xz | |
Revert "scsi: sd: Keep disk read-only when re-reading partition"
commit 8acf608e602f6ec38b7cc37b04c80f1ce9a1a6cc upstream.
This reverts commit 20bd1d026aacc5399464f8328f305985c493cde3.
This patch introduced regressions for devices that come online in
read-only state and subsequently switch to read-write.
Given how the partition code is currently implemented it is not
possible to persist the read-only flag across a device revalidate
call. This may need to get addressed in the future since it is common
for user applications to proactively call BLKRRPART.
Reverting this commit will re-introduce a regression where a
device-initiated revalidate event will cause the admin state to be
forgotten. A separate patch will address this issue.
Fixes: 20bd1d026aac ("scsi: sd: Keep disk read-only when re-reading partition")
Cc: <stable@vger.kernel.org>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/hmac.c')
0 files changed, 0 insertions, 0 deletions