From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Hannes Reinecke <hare@suse.com>,
Shaun Tancheff <shaun@tancheff.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <damien.lemoal@dc.com>,
Aravind Ramesh <Aravind.Ramesh@wdc.com>,
Adam Manzanares <a.manzanares@samsung.com>,
Himanshu Madhani <himanshu.madhani@oracle.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Jens Axboe <axboe@fb.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/2] blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
Date: Mon, 9 Aug 2021 10:04:56 +0000 [thread overview]
Message-ID: <YRD9x3+DOTFK82pr@x1-carbon> (raw)
In-Reply-To: <PH0PR04MB7416400F3559116FA3192A5F9BF69@PH0PR04MB7416.namprd04.prod.outlook.com>
On Mon, Aug 09, 2021 at 09:58:17AM +0000, Johannes Thumshirn wrote:
> On 09/08/2021 11:50, Niklas Cassel wrote:
> > From: Niklas Cassel <niklas.cassel@wdc.com>
> >
> > A user space process should not need the CAP_SYS_ADMIN capability set
> > in order to perform a BLKREPORTZONE ioctl.
> >
> > Getting the zone report is required in order to get the write pointer.
> > Neither read() nor write() requires CAP_SYS_ADMIN, so it is reasonable
> > that a user space process that can read/write from/to the device, also
> > can get the write pointer. (Since e.g. writes have to be at the write
> > pointer.)
> >
> > Fixes: 3ed05a987e0f ("blk-zoned: implement ioctls")
> > Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> > Reviewed-by: Damien Le Moal <damien.lemoal@dc.com>
> Nit: Missing 'w'
Seems like Damien's email had a typo in his original reply:
https://patchwork.kernel.org/project/linux-block/patch/20210614122303.154378-3-Niklas.Cassel@wdc.com/#24252237
Surprised that he doesn't have a shortcut to paste his Reviewed-by tag,
considering the amount of patches that he reviews :)
> > Reviewed-by: Aravind Ramesh <aravind.ramesh@wdc.com>
> > Reviewed-by: Adam Manzanares <a.manzanares@samsung.com>
> > Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
> > Cc: stable@vger.kernel.org # v4.10+
> > ---
> Looks good,
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>
>
prev parent reply other threads:[~2021-08-09 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 9:50 [PATCH v4 0/2] allow blk-zoned ioctls without CAP_SYS_ADMIN Niklas Cassel
2021-08-09 9:50 ` [PATCH v4 1/2] blk-zoned: allow zone management send operations " Niklas Cassel
2021-08-09 9:57 ` Johannes Thumshirn
2021-08-09 9:50 ` [PATCH v4 2/2] blk-zoned: allow BLKREPORTZONE " Niklas Cassel
2021-08-09 9:58 ` Johannes Thumshirn
2021-08-09 10:04 ` Niklas Cassel [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=YRD9x3+DOTFK82pr@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=Aravind.Ramesh@wdc.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=a.manzanares@samsung.com \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@dc.com \
--cc=hare@suse.com \
--cc=himanshu.madhani@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shaun@tancheff.com \
--cc=stable@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