This appears to be due to an intentional change in behavior to improve
security which I believe was introduced in 19.10. To restore the older
behavior, create `/etc/sysctl.d/protect-links.conf` with the contents:

fs.protected_regular = 0

Then restart procps:

sudo systemctl restart procps.service

To verify run:

$ sudo sysctl fs.protected_regular
fs.protected_regular = 0

References:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=30aba6656f61ed44cba445a3c0d38b296fa9e8f5
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915797

** Bug watch added: Debian Bug tracker #915797
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915797

** Changed in: linux (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875667

Title:
  root cannot flock user file in rwt dir if parent gives limited access

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875667/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to