On Wed 2017-08-23 (10:16), Dmitrii Tcvetkov wrote: > > >Also in https://btrfs.wiki.kernel.org/index.php/Mount_options > > >"user_subvol_rm_allowed (...) Use with caution." > > > > > >Why? What is the problem? > > > > Because with the mount option any user can delete any subvolume, > > including root one (subvol_id=5) > > Apologies, it works somewhat different: > filesystem doesn't allow to delete subvolume with id 5 and POSIX access > is checked before deleting subvolume with user_subvol_rm_allowed mount > option. I have tested it already :-) So, still: What is the problem with user_subvol_rm_allowed? -- Ullrich Horlacher Server und Virtualisierung Rechenzentrum TIK Universitaet Stuttgart E-Mail: horlacher@xxxxxxxxxxxxxxxxxxxx Allmandring 30a Tel: ++49-711-68565868 70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/ REF:<20170823101635.114d02d2@job> -- 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
