From: Christoph Hellwig <hch@lst.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Ilya Dryomov <idryomov@gmail.com>, Song Liu <song@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>,
linux-block@vger.kernel.org, ceph-devel@vger.kernel.org,
linux-bcache@vger.kernel.org, linux-raid@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH, RFC 11/10] block: propagate BLKROSET to all partitions
Date: Wed, 11 Nov 2020 09:03:34 +0100 [thread overview]
Message-ID: <20201111080334.GA23062@lst.de> (raw)
In-Reply-To: <yq1imacecwz.fsf@ca-mkp.ca.oracle.com>
On Tue, Nov 10, 2020 at 11:38:22PM -0500, Martin K. Petersen wrote:
>
> Christoph,
>
> > When setting the whole device read-only (or clearing the read-only
> > state), also update the policy for all partitions. The s390 dasd
> > driver has awlways been doing this and it makes a lot of sense.
>
> For your amusement, here's my attempt at addressing this from a while
> back. Can't remember exactly why this stranded, I even wrote blktests
> for it...
I added you to the Cc list because I had a vague memory that you were
looking into this area a while ago.
I actually think your patch that goes further is the right thing to do,
and I was going to look into something similar for a problem with
hardware read-only namespaces in NVMe. I think I'll take your patch
as a starting point and will work from there.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-raid@vger.kernel.org, Jan Hoeppner <hoeppner@linux.ibm.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-s390@vger.kernel.org, Richard Weinberger <richard@nod.at>,
ceph-devel@vger.kernel.org, linux-block@vger.kernel.org,
Song Liu <song@kernel.org>,
linux-bcache@vger.kernel.org, linux-mtd@lists.infradead.org,
Stefan Haberland <sth@linux.ibm.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Ilya Dryomov <idryomov@gmail.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH, RFC 11/10] block: propagate BLKROSET to all partitions
Date: Wed, 11 Nov 2020 09:03:34 +0100 [thread overview]
Message-ID: <20201111080334.GA23062@lst.de> (raw)
In-Reply-To: <yq1imacecwz.fsf@ca-mkp.ca.oracle.com>
On Tue, Nov 10, 2020 at 11:38:22PM -0500, Martin K. Petersen wrote:
>
> Christoph,
>
> > When setting the whole device read-only (or clearing the read-only
> > state), also update the policy for all partitions. The s390 dasd
> > driver has awlways been doing this and it makes a lot of sense.
>
> For your amusement, here's my attempt at addressing this from a while
> back. Can't remember exactly why this stranded, I even wrote blktests
> for it...
I added you to the Cc list because I had a vague memory that you were
looking into this area a while ago.
I actually think your patch that goes further is the right thing to do,
and I was going to look into something similar for a problem with
hardware read-only namespaces in NVMe. I think I'll take your patch
as a starting point and will work from there.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-11-11 8:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 14:08 [PATCH, RFC 11/10] block: propagate BLKROSET to all partitions Christoph Hellwig
2020-11-06 14:08 ` Christoph Hellwig
2020-11-06 19:16 ` Stefan Haberland
2020-11-06 19:16 ` Stefan Haberland
2020-11-07 7:28 ` Coly Li
2020-11-07 7:28 ` Coly Li
2020-11-11 4:38 ` Martin K. Petersen
2020-11-11 4:38 ` Martin K. Petersen
2020-11-11 8:03 ` Christoph Hellwig [this message]
2020-11-11 8:03 ` Christoph Hellwig
2020-11-11 16:53 ` Martin K. Petersen
2020-11-11 16:53 ` Martin K. Petersen
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=20201111080334.GA23062@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=ceph-devel@vger.kernel.org \
--cc=hoeppner@linux.ibm.com \
--cc=idryomov@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=song@kernel.org \
--cc=sth@linux.ibm.com \
--cc=vigneshr@ti.com \
/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.