From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
axboe@kernel.dk, dgilbert@interlog.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com,
Ryan Attard <ryanattard@ryanattard.info>
Subject: Re: [PATCH 1/1 RESEND] Allow non-root users to perform ZBC commands.
Date: Tue, 10 Mar 2020 23:10:37 -0400 [thread overview]
Message-ID: <yq17dzrr3gy.fsf@oracle.com> (raw)
In-Reply-To: <20200226170518.92963-2-ryanattard@ryanattard.info> (Ryan Attard's message of "Wed, 26 Feb 2020 11:05:19 -0600")
Damien: Please opine.
> Allow users with read permissions to issue REPORT ZONE commands and
> users with write permissions to manage zones on block devices supporting
> the ZBC specification.
>
> Signed-off-by: Ryan Attard <ryanattard@ryanattard.info>
> ---
> block/scsi_ioctl.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/block/scsi_ioctl.c b/block/scsi_ioctl.c
> index b4e73d5dd5c2..ef722f04f88a 100644
> --- a/block/scsi_ioctl.c
> +++ b/block/scsi_ioctl.c
> @@ -193,6 +193,10 @@ static void blk_set_cmd_filter_defaults(struct blk_cmd_filter *filter)
> __set_bit(GPCMD_LOAD_UNLOAD, filter->write_ok);
> __set_bit(GPCMD_SET_STREAMING, filter->write_ok);
> __set_bit(GPCMD_SET_READ_AHEAD, filter->write_ok);
> +
> + /* ZBC Commands */
> + __set_bit(ZBC_OUT, filter->write_ok);
> + __set_bit(ZBC_IN, filter->read_ok);
> }
>
> int blk_verify_command(unsigned char *cmd, fmode_t mode)
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-03-11 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 17:05 [PATCH 0/1 RESEND] Allow non-root users to perform ZBC commands Ryan Attard
2020-02-26 17:05 ` [PATCH 1/1 " Ryan Attard
2020-03-11 3:10 ` Martin K. Petersen [this message]
2020-03-11 3:48 ` Damien Le Moal
2020-03-12 3:15 ` 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=yq17dzrr3gy.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=dgilbert@interlog.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ryanattard@ryanattard.info \
/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