On 12/11/22 8:59 PM, Ming Lei wrote: > 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... I think timing was just a tad late on this. OK if we defer for 6.3, or are there strong arguments for 6.2? -- Jens Axboe
