From: Aravind Ramesh <Aravind.Ramesh@wdc.com>
To: Jens Axboe <axboe@kernel.dk>, Jens Axboe <axboe@fb.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Niklas Cassel <Niklas.Cassel@wdc.com>
Subject: RE: [PATCH v3 0/2] allow blk-zoned ioctls without CAP_SYS_ADMIN
Date: Wed, 21 Jul 2021 05:04:36 +0000 [thread overview]
Message-ID: <BYAPR04MB4056026E85897DA145B45BB08CE39@BYAPR04MB4056.namprd04.prod.outlook.com> (raw)
In-Reply-To: <YOLsgFzIBlg/H/ba@x1-carbon.lan>
> -----Original Message-----
> From: Niklas Cassel <Niklas.Cassel@wdc.com>
> Sent: Monday, July 5, 2021 4:57 PM
> To: Jens Axboe <axboe@kernel.dk>; Jens Axboe <axboe@fb.com>
> Cc: linux-block@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v3 0/2] allow blk-zoned ioctls without CAP_SYS_ADMIN
>
> On Mon, Jun 28, 2021 at 09:20:15AM +0200, Niklas Cassel wrote:
> > On Mon, Jun 14, 2021 at 12:23:19PM +0000, Niklas Cassel wrote:
> > > From: Niklas Cassel <niklas.cassel@wdc.com>
> > >
> > > Allow the following blk-zoned ioctls: BLKREPORTZONE, BLKRESETZONE,
> > > BLKOPENZONE, BLKCLOSEZONE, and BLKFINISHZONE to be performed without
> > > CAP_SYS_ADMIN.
> > >
> > > Neither read() nor write() requires CAP_SYS_ADMIN, and considering
> > > the close relationship between read()/write() and these ioctls,
> > > there is no reason to require CAP_SYS_ADMIN for these ioctls either.
> > >
> > > Changes since v2:
> > > -Drop the FMODE_READ check from patch 2/2.
> > > Right now it is possible to open() the device with O_WRONLY and get
> > > the zone report from that fd. Therefore adding a FMODE_READ check on
> > > BLKREPORTZONE would break existing applications.
> > > Instead, just remove the existing CAP_SYS_ADMIN check.
> > >
> > >
> > > Niklas Cassel (2):
> > > blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
> > > blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
> > >
> > > block/blk-zoned.c | 6 ------
> > > 1 file changed, 6 deletions(-)
> > >
> > > --
> > > 2.31.1
> >
> > Hello Jens,
> >
> >
> > A gentle ping on this series.
> >
> > I think it has sufficient Reviewed-by tags by now.
> >
> >
> > Kind regards,
> > Niklas
>
> Hello again Jens,
>
>
> any chance of this series being picked up?
>
Hello Jens,
Gentle ping.
Could you please take a look at this series ?
Thanks,
Aravind
>
> Kind regards,
> Niklas
prev parent reply other threads:[~2021-07-21 5:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 12:23 [PATCH v3 0/2] allow blk-zoned ioctls without CAP_SYS_ADMIN Niklas Cassel
2021-06-14 12:23 ` [PATCH v3 1/2] blk-zoned: allow zone management send operations " Niklas Cassel
2021-06-16 13:42 ` Aravind Ramesh
2021-06-18 14:48 ` Adam Manzanares
2021-06-18 17:56 ` Himanshu Madhani
2021-06-14 12:23 ` [PATCH v3 2/2] blk-zoned: allow BLKREPORTZONE " Niklas Cassel
2021-06-16 2:29 ` Damien Le Moal
2021-06-16 13:43 ` Aravind Ramesh
2021-06-18 14:49 ` Adam Manzanares
2021-06-18 17:57 ` Himanshu Madhani
2021-06-28 7:20 ` [PATCH v3 0/2] allow blk-zoned ioctls " Niklas Cassel
2021-07-05 11:26 ` Niklas Cassel
2021-07-21 5:04 ` Aravind Ramesh [this message]
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=BYAPR04MB4056026E85897DA145B45BB08CE39@BYAPR04MB4056.namprd04.prod.outlook.com \
--to=aravind.ramesh@wdc.com \
--cc=Niklas.Cassel@wdc.com \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).