[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH0PR04MB7416400F3559116FA3192A5F9BF69@PH0PR04MB7416.namprd04.prod.outlook.com>
Date: Mon, 9 Aug 2021 09:58:17 +0000
From: Johannes Thumshirn <Johannes.Thumshirn@....com>
To: Niklas Cassel <Niklas.Cassel@....com>,
Jens Axboe <axboe@...nel.dk>,
Damien Le Moal <Damien.LeMoal@....com>,
Hannes Reinecke <hare@...e.com>,
Shaun Tancheff <shaun@...cheff.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
CC: Damien Le Moal <damien.lemoal@...com>,
Aravind Ramesh <Aravind.Ramesh@....com>,
Adam Manzanares <a.manzanares@...sung.com>,
Himanshu Madhani <himanshu.madhani@...cle.com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Jens Axboe <axboe@...com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 2/2] blk-zoned: allow BLKREPORTZONE without
CAP_SYS_ADMIN
On 09/08/2021 11:50, Niklas Cassel wrote:
> From: Niklas Cassel <niklas.cassel@....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@....com>
> Reviewed-by: Damien Le Moal <damien.lemoal@...com>
Nit: Missing 'w'
> Reviewed-by: Aravind Ramesh <aravind.ramesh@....com>
> Reviewed-by: Adam Manzanares <a.manzanares@...sung.com>
> Reviewed-by: Himanshu Madhani <himanshu.madhani@...cle.com>
> Cc: stable@...r.kernel.org # v4.10+
> ---
Looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@....com>
Powered by blists - more mailing lists