Activity log for bug #518926

Date Who What changed Old value New value Message
2010-02-08 17:44:09 Dave Martin bug added bug
2010-02-08 17:44:09 Dave Martin attachment added possible fix http://launchpadlibrarian.net/38898001/plymouth_Fix-incorrect-maxevents-parameter-to-epoll_wait.patch
2010-02-08 18:01:49 Brian Murray tags patch
2010-02-08 18:05:37 Dave Martin description Binary package hint: plymouth In ply_event_loop_process_pending_events(), sizeof (events) is passed for the maxevents parameter to epoll_wait(). events is a pointer, to sizeof (events) is 4 or 8 on most architectures. This seems unlikely to have been what was intended. Is PLY_EVENT_LOOP_NUM_EVENT_HANDLERS supposed to be passed for maxevents instead? (This is the number if event structures allocated to events.) If so, the attached patch ought to fix it. Binary package hint: plymouth In ply_event_loop_process_pending_events(), sizeof (events) is passed for the maxevents parameter to epoll_wait(). events is a pointer, to sizeof (events) is 4 or 8 on most architectures. This seems unlikely to have been what was intended. Is PLY_EVENT_LOOP_NUM_EVENT_HANDLERS supposed to be passed for maxevents instead? (This is the number if event structures allocated to events.) If so, the attached patch ought to fix it. This bug was found while investigating the following issue, but is probably not directly related: * https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/518937 (ply_event_loop_process_pending_events can block, causing mountall to deadlock)
2010-02-08 18:07:46 Dave Martin description Binary package hint: plymouth In ply_event_loop_process_pending_events(), sizeof (events) is passed for the maxevents parameter to epoll_wait(). events is a pointer, to sizeof (events) is 4 or 8 on most architectures. This seems unlikely to have been what was intended. Is PLY_EVENT_LOOP_NUM_EVENT_HANDLERS supposed to be passed for maxevents instead? (This is the number if event structures allocated to events.) If so, the attached patch ought to fix it. This bug was found while investigating the following issue, but is probably not directly related: * https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/518937 (ply_event_loop_process_pending_events can block, causing mountall to deadlock) Binary package hint: plymouth Ubuntu lucid plymouth 0.8.0~-9 In ply_event_loop_process_pending_events(), sizeof (events) is passed for the maxevents parameter to epoll_wait(). events is a pointer, to sizeof (events) is 4 or 8 on most architectures. This seems unlikely to have been what was intended. Is PLY_EVENT_LOOP_NUM_EVENT_HANDLERS supposed to be passed for maxevents instead? (This is the number if event structures allocated to events.) If so, the attached patch ought to fix it. This bug was found while investigating the following issue, but is probably not directly related:  * https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/518937 (ply_event_loop_process_pending_events can block, causing mountall to deadlock)
2010-02-08 19:11:29 Brian Murray removed subscriber Ubuntu Review Team
2010-02-08 19:11:52 Brian Murray plymouth (Ubuntu): importance Undecided Medium
2010-02-08 19:11:54 Brian Murray plymouth (Ubuntu): status New Triaged
2010-03-13 10:44:47 Scott James Remnant (Canonical) plymouth (Ubuntu): importance Medium Low
2010-03-15 11:44:18 Daniel Holbach removed subscriber Ubuntu Sponsors for main
2010-05-16 23:10:51 Benjamin Drung removed subscriber Ubuntu Sponsors Team
2011-03-24 13:08:20 Colin Watson plymouth (Ubuntu): status Triaged Fix Committed
2011-03-24 13:09:14 Launchpad Janitor branch linked lp:ubuntu/plymouth
2011-03-24 14:20:12 Launchpad Janitor plymouth (Ubuntu): status Fix Committed Fix Released