Hi Ben,
> (The log message about Write Protect status also reports the
> underlying SCSI device flag and not the combined ro flag, but maybe
> that was intentional.)
I'd prefer for the printk in question to reflect the device-reported
state, not the state of the block device.
> I think this co
Hi Ben,
On 06/13/2018 05:25 PM, Ben Hutchings wrote:
> On Mon, 2018-05-28 at 12:01 +0200, Greg Kroah-Hartman wrote:
>> 4.4-stable review patch. If anyone has any objections, please let me know.
>>
>> --
>>
>> From: Jeremy Cline
>>
>> [ Upstream commit 20bd1d026aacc5399464f8328f30
On Mon, 2018-05-28 at 12:01 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Jeremy Cline
>
> [ Upstream commit 20bd1d026aacc5399464f8328f305985c493cde3 ]
>
> If the read-only flag is true on a SCSI
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jeremy Cline
[ Upstream commit 20bd1d026aacc5399464f8328f305985c493cde3 ]
If the read-only flag is true on a SCSI disk, re-reading the partition
table sets the flag back to false.
To observe t
4 matches
Mail list logo