do the resulting semantics match (or resemble) the semantics provided by other facilities that allow non-superusers to mount and unmount file systems? If all "user mountable file systems" are provided either by the FUSE layer (but that is concerned with providing the FS, not mounting it) or by setuid tools, this question may be safe to ignore. On Tue, Oct 26, 2010 at 2:20 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote: > Add a mount option user_subvol_rm_allowed that allows users to delete a > (potentially non-empty!) subvol when they would otherwise we allowed to do > an rmdir(2). ÂWe duplicate the may_delete() checks from the core VFS code > to implement identical security checks (minus the directory size check). > We additionally require that the user has write+exec permission on the > subvol root inode. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
