allow vs. usermount [Re: ZFS patches.]

[Pawel Jakub Dawidek]

On Mon, Jul 28, 2008 at 11:16:37PM +0200, Max Laier wrote:
> On Sunday 27 July 2008 14:54:13 Pawel Jakub Dawidek wrote:
> > If you have any questions, please use mailing lists
> > (freebsd-fs at FreeBSD.org would be the best).
> 
> Short exercise:
> | $ whoami
> | mlaier
> | $ zfs list
> | NAME          USED  AVAIL  REFER  MOUNTPOINT
> | tank          104K   228G    19K  /tank
> | tank/mlaier    18K   228G    18K  /tank/mlaier
> | $ zfs allow tank/mlaier
> | -------------------------------------------------------------
> | Local+Descendent permissions on (tank/mlaier)
> |         user mlaier create,destroy,mount,snapshot
> | -------------------------------------------------------------
> | $ zfs create tank/mlaier/test
> | cannot mount 'tank/mlaier/test': Insufficient privileges
> | filesystem successfully created, but not mounted
> 
> This is obviously due to the check in vfs_mount.c patched line 851:
> 
> 	if (jailed(td->td_ucred) || usermount == 0) {
> 
> the question is, should this be tuned to allow for the finer grained zfs 
> permissions to take effect or will we force usermount to use zfs allow mount?

Current plan is to document it in the same way ZFS within a jail is
documented in zfs(8). Yes, one needs to set vfs.usermount=1 by hand.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20080728/e92a1b6a/attachment.pgp