From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
ZiyangZhang <ZiyangZhang@linux.alibaba.com>,
ming.lei@redhat.com
Subject: Re: [PATCH V3 0/6] ublk_drv: add mechanism for supporting unprivileged ublk device
Date: Mon, 12 Dec 2022 11:59:53 +0800 [thread overview]
Message-ID: <Y5anOZyJBCes1XEo@T590> (raw)
In-Reply-To: <20221207123305.937678-1-ming.lei@redhat.com>
On Wed, Dec 07, 2022 at 08:32:59PM +0800, Ming Lei wrote:
> Hello,
>
> Stefan Hajnoczi suggested un-privileged ublk device[1] for container
> use case.
>
> So far only administrator can create/control ublk device which is too
> strict and increase system administrator burden, and this patchset
> implements un-privileged ublk device:
>
> - any user can create ublk device, which can only be controlled &
> accessed by the owner of the device or administrator
>
> For using such mechanism, system administrator needs to deploy two
> simple udev rules[2] after running 'make install' in ublksrv.
>
> Userspace(ublksrv):
>
> https://github.com/ming1/ubdsrv/tree/unprivileged-ublk
>
> 'ublk add -t $TYPE --un_privileged' is for creating one un-privileged
> ublk device if the user is un-privileged.
>
>
> [1] https://lore.kernel.org/linux-block/YoOr6jBfgVm8GvWg@stefanha-x1.localdomain/
> [2] https://github.com/ming1/ubdsrv/blob/unprivileged-ublk/README.rst#un-privileged-mode
>
> V3:
> - don't warn on invalid user input for setting devt parameter, as
> suggested by Ziyang, patch 4/6
> - fix one memory corruption issue, patch 6/6
Hello Guys,
Ping...
thanks,
Ming
next prev parent reply other threads:[~2022-12-12 4:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 12:32 [PATCH V3 0/6] ublk_drv: add mechanism for supporting unprivileged ublk device Ming Lei
2022-12-07 12:33 ` [PATCH V3 1/6] ublk_drv: remove nr_aborted_queues from ublk_device Ming Lei
2022-12-07 12:33 ` [PATCH V3 2/6] ublk_drv: don't probe partitions if the ubq daemon isn't trusted Ming Lei
2022-12-07 12:33 ` [PATCH V3 3/6] ublk_drv: move ublk_get_device_from_id into ublk_ctrl_uring_cmd Ming Lei
2022-12-07 12:33 ` [PATCH V3 4/6] ublk_drv: add device parameter UBLK_PARAM_TYPE_DEVT Ming Lei
2022-12-07 12:33 ` [PATCH V3 5/6] ublk_drv: add module parameter of ublks_max for limiting max allowed ublk dev Ming Lei
2022-12-07 12:33 ` [PATCH V3 6/6] ublk_drv: add mechanism for supporting unprivileged ublk device Ming Lei
2023-01-03 20:35 ` Jonathan Corbet
2023-01-04 8:19 ` Ming Lei
2022-12-12 3:59 ` Ming Lei [this message]
2022-12-14 17:54 ` [PATCH V3 0/6] " Jens Axboe
2022-12-15 0:35 ` Ming Lei
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=Y5anOZyJBCes1XEo@T590 \
--to=ming.lei@redhat.com \
--cc=ZiyangZhang@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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