If you see my follow-on patch, it allows disabling the quota limit for folks with cap_sys_resource per filesystem. I don't want to have any process to be able to turn off quota limits, but just the process that is the logrotator (and has the proper capabilities). Unfortunately, most folks don't lock down their capabilities, so I agree, making it blindly based on capabilities seems like a poor idea.
On Fri, May 5, 2017 at 11:22 AM, David Sterba <dste...@suse.cz> wrote: > On Fri, Apr 21, 2017 at 07:27:23AM -0500, Sargun Dhillon wrote: >> What do you think about putting this behaviour behind a sysctl? Seems >> better than to start introducing a new mechanism of marking tasks? > > Technically it's easy to add own btrfs-specific ioctl, temporarily > turning off quota limits, but I'm still not sure about all the > consequences as this would apply to the whole system, no? The > capabilities are per process, much more fine grained. I don't have other > ideas how to address the problem though. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
