From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
ZiyangZhang <ZiyangZhang@linux.alibaba.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
ming.lei@redhat.com
Subject: Re: [PATCH V4 0/6] ublk_drv: add mechanism for supporting unprivileged ublk device
Date: Tue, 17 Jan 2023 17:36:37 +0800 [thread overview]
Message-ID: <Y8ZsJefw/Q6ArMzk@T590> (raw)
In-Reply-To: <20230106041711.914434-1-ming.lei@redhat.com>
On Fri, Jan 06, 2023 at 12:17:05PM +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
>
> V4:
> - only allow to create unprivileged udev for current user, as
> suggested by Jonathan Corbet
> - fix misc bug for handling failure
> - add detailed document
> - update userspace
Hello Guys,
Ping...
Thanks,
Ming
next prev parent reply other threads:[~2023-01-17 9:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 4:17 [PATCH V4 0/6] ublk_drv: add mechanism for supporting unprivileged ublk device Ming Lei
2023-01-06 4:17 ` [PATCH V4 1/6] ublk_drv: remove nr_aborted_queues from ublk_device Ming Lei
2023-01-06 4:17 ` [PATCH V4 2/6] ublk_drv: don't probe partitions if the ubq daemon isn't trusted Ming Lei
2023-01-06 4:17 ` [PATCH V4 3/6] ublk_drv: move ublk_get_device_from_id into ublk_ctrl_uring_cmd Ming Lei
2023-01-06 4:17 ` [PATCH V4 4/6] ublk_drv: add device parameter UBLK_PARAM_TYPE_DEVT Ming Lei
2023-01-06 4:17 ` [PATCH V4 5/6] ublk_drv: add module parameter of ublks_max for limiting max allowed ublk dev Ming Lei
2023-01-06 4:17 ` [PATCH V4 6/6] ublk_drv: add mechanism for supporting unprivileged ublk device Ming Lei
2023-01-06 15:33 ` kernel test robot
2023-01-17 9:36 ` Ming Lei [this message]
2023-01-17 17:23 ` [PATCH V4 0/6] " Jens Axboe
2023-01-30 22:20 ` Stefan Hajnoczi
2023-01-31 2:30 ` 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=Y8ZsJefw/Q6ArMzk@T590 \
--to=ming.lei@redhat.com \
--cc=ZiyangZhang@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-block@vger.kernel.org \
--cc=stefanha@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.