From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Oleksii Kurochko <olkuroch@cisco.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-block@vger.kernel.org
Subject: Re: split hard read-only vs read-only policy
Date: Fri, 13 Nov 2020 13:44:13 -0500 [thread overview]
Message-ID: <yq14klt9k0a.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20201113084702.4164912-1-hch@lst.de> (Christoph Hellwig's message of "Fri, 13 Nov 2020 09:46:59 +0100")
Christoph,
> 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.
Looks good in general but two of my test cases failed. Will debug.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-11-13 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 8:46 split hard read-only vs read-only policy Christoph Hellwig
2020-11-13 8:47 ` [PATCH 1/3] block: Fix read-only block device setting after revalidate Christoph Hellwig
2020-11-16 3:55 ` Martin K. Petersen
2020-11-16 17:37 ` Christoph Hellwig
2020-11-13 8:47 ` [PATCH 2/3] rbd: remove the ->set_read_only methods Christoph Hellwig
2020-11-13 8:47 ` [PATCH 3/3] block: replace hd_struct.make_it_fail with a flag Christoph Hellwig
2020-11-13 18:44 ` Martin K. Petersen [this message]
2020-11-13 19:51 ` split hard read-only vs read-only policy Sagi Grimberg
2020-11-14 9:18 ` Christoph Hellwig
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=yq14klt9k0a.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=olkuroch@cisco.com \
--cc=sagi@grimberg.me \
/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.