From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:39122 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725828AbgKKIDq (ORCPT ); Wed, 11 Nov 2020 03:03:46 -0500 Date: Wed, 11 Nov 2020 09:03:34 +0100 From: Christoph Hellwig Subject: Re: [PATCH, RFC 11/10] block: propagate BLKROSET to all partitions Message-ID: <20201111080334.GA23062@lst.de> References: <20201106140817.GA23557@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-ID: To: "Martin K. Petersen" Cc: Christoph Hellwig , Jens Axboe , Ilya Dryomov , Song Liu , Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Stefan Haberland , Jan Hoeppner , 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 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.