Cosmic upload is currently tested, also prepared the SRU Template for the latter upload to Bionic.
** Description changed: + [Impact] + + * Certain configurations will fall into a busy loop and never fully + start + + * Fix by backporting from upstream + + [Test Case] + + 1. install packages + $ sudo apt install rpcbind quota + 2. to let the service start at all one need: + - Add ",usrquota" to your fstab options somewhere + - Add a fake export to /etc/exports like + /tmp 127.0.0.1 + 3. offending config: + Only then will quotarpc.service start, but it does not expose the + faulty behavior yet, to get that set a special port via + RPCRQUOTADOPTS="-p 599" in /etc/default/quota. + + Now you can run systemctl restart quota and it will lock up in 100% CPU. + + [Regression Potential] + + * It is an extra listen and setsockipt call. While it is correct to do + those (that is the fix) there might exist cases we didn't hit in + testing where those calls fail and break it. + Yet since it lies on a code path that currently is affected by the 100% + cpu hog that should (tm) not be a huge regression potential. + At least both paths - if failing - have proper error reporting so a + user will know what broke and is not just failing without knowing why + out of a sudden. + + [Other Info] + + * n/a + + --- + This happens on Ubuntu 18.04 with package quota 4.04-2 installed. The bug is already known and a patch is available: https://sourceforge.net/p/linuxquota/feature-requests/16/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774431 Title: rpc.rquotad takes 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quota/+bug/1774431/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
