This was nominated as a 8.04.3 candidate by Steve Langasek, so here is
the SRU report, we won't wait for the other bug to be ready since it's
stuck on hardware availability for reproduction.
Hardy SRU report
Bug impact:
In certain conditions groupd, fenced, and dlm_controld all have the potential
to enter infinite/tight loops surrounding poll(2) due to a file descriptor
being closed and not correctly handled. The poll loop for these daemons checks
for POLLHUP, but not POLLERR or POLLNVAL. As such, file descriptors in these
states are unhandled.
Versions affected: Hardy
Fix in development branch: Was fixed in >= Intrepid by integration of a later,
fixed, upstream release.
Minimal patch: see comment 2 just above.
TEST CASE:
This is difficult to reproduce as it supposes a full RHCS setup and hitting the
situation where those daemons enter the loop.
Regression potential:
Looking at the patch, regression potential is very low. It was taken from the
RedHat bug and was later successfully integrated in the following RHCS
releases. Users running the version from my PPA all reported success without
any nasty side-effect.
** Changed in: redhat-cluster (Ubuntu Hardy)
Assignee: Thierry Carrez (tcarrez) => (unassigned)
Status: Triaged => Confirmed
--
After ran the command fence_tool dump, the fenced process will take 100% CPU
usage
https://bugs.launchpad.net/bugs/290399
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
