split hard read-only vs read-only policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jens Axboe <axboe@xxxxxxxxx>
Subject: split hard read-only vs read-only policy
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 13 Nov 2020 09:46:59 +0100
Cc: "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, Oleksii Kurochko <olkuroch@xxxxxxxxx>, Sagi Grimberg <sagi@xxxxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx

Hi Jens,

this series resurrects a patch from Martin to properly split the flag
indicating a disk has been set read-only by the hardware vs the userspace
policy set through the BLKROSET ioctl.

Follow-Ups:
- Re: split hard read-only vs read-only policy
  - From: Sagi Grimberg
- Re: split hard read-only vs read-only policy
  - From: Martin K. Petersen
- [PATCH 1/3] block: Fix read-only block device setting after revalidate
  - From: Christoph Hellwig
- [PATCH 3/3] block: replace hd_struct.make_it_fail with a flag
  - From: Christoph Hellwig
- [PATCH 2/3] rbd: remove the ->set_read_only methods
  - From: Christoph Hellwig

Prev by Date: [PATCH 3/3] block: replace hd_struct.make_it_fail with a flag
Next by Date: [PATCH 1/3] block: Fix read-only block device setting after revalidate
Previous by thread: [RFC] Enhancement of loop driver?
Next by thread: [PATCH 2/3] rbd: remove the ->set_read_only methods
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux