From: Ryan Attard <ryanattard@ryanattard.info>
To: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Cc: ryanattard@ryanattard.info, axboe@kernel.dk,
dgilbert@interlog.com, jejb@linux.vnet.ibm.com,
martin.petersen@oracle.com
Subject: [PATCH 0/1 RESEND] Allow non-root users to perform ZBC commands.
Date: Wed, 26 Feb 2020 11:05:17 -0600 [thread overview]
Message-ID: <20200226170518.92963-1-ryanattard@ryanattard.info> (raw)
Resending since I missed some emails on the first:
The source of this issue is that a group is configured that allows a service
user to perform read and writes to a specific set of disks, and the permissions
on the sd device entries for a host managed device have permissions 0660, same
as the sg device entry. Operations succeed on the sg device (since there is
a different code path for handling those operations).
There was some hand wringing around adding CAP_SYS_RAWIO capabilities to that
user, since it includes things like /dev/mem access which was not desired or
required to perform disk write operations.
Example failure:
root@device_with_zbc_disks:~# su -s /bin/bash -c 'sg_rep_zones -vv /dev/sdh -m 128' USER_LOW_PERMS
open /dev/sdh with flags=0x802
Report zones cdb: 95 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00
ioctl(SG_IO v3) failed: Operation not permitted (errno=1)
report zones: pass through os error: Operation not permitted
Report zones command: Sense category: -1
root@device_with_zbc_disks:~# su -s /bin/bash -c 'sg_rep_zones -vv /dev/sg7 -m 128' USER_LOW_PERMS
open /dev/sdh with flags=0x802
Report zones cdb: 95 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00
zl_len available is 2624, response length is 128
Report zones response:
Same=0: zone type and length may differ in each descriptor
<snip>
Example with patch:
root@device_with_zbc_disks:~# su -s /bin/bash -c 'sg_rep_zones -vv /dev/sdh -m 128' USER_LOW_PERMS
open /dev/sdh with flags=0x802
Report zones cdb: 95 00 00 00 00 00 00 00 00 00 00 00 00 80 00 00
zl_len available is 2624, response length is 128
Report zones response:
Same=0: zone type and length may differ in each descriptor
<snip>
Thanks,
Ryan
next reply other threads:[~2020-02-26 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 17:05 Ryan Attard [this message]
2020-02-26 17:05 ` [PATCH 1/1 RESEND] Allow non-root users to perform ZBC commands Ryan Attard
2020-03-11 3:10 ` Martin K. Petersen
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=20200226170518.92963-1-ryanattard@ryanattard.info \
--to=ryanattard@ryanattard.info \
--cc=axboe@kernel.dk \
--cc=dgilbert@interlog.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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