acpid locking up
Posted: Wed Oct 02, 2002 4:23 pm
acpid is causing huge problems on my system, but works correctly with an identical non-grsecurity kernel.
What happens is this: it starts normally, but if you subsequently try to read its /proc/pid directory, the process reading the information hangs and can only be terminated by the kernel (sysrq-k). This means that ps crashes as soon as it reaches acpid (without printing anything for it) and even trying to ls /proc/pid just to display the contents locks up.
acpid seems not to be working either during this - it doesn't respond to the power button, in any case.
This causes all kinds of things to go horribly wrong - start-stop-daemon can't cope..etc.
Using an otherwise identical kernel without grsecurity enabled, it doesn't do this.
I haven't got the ACL system or any sysctl-controlled options turned on at all (I have not yet configured grsecurity), which vastly limits the scope of the bug. I can't get strace to attach to acpid, I can't view its maps file, I can't really get any debugging information at all =(
I'm building a selection of kernels with different options enabled/disabled to try and localise the problem, but I'm posting this now in case anyone has any bright ideas that could save me some time =)
I'm using grsecurity 1.9.7 and Debian's 2.4.19 source.
Followup will come once I've experimented more..
Torne
What happens is this: it starts normally, but if you subsequently try to read its /proc/pid directory, the process reading the information hangs and can only be terminated by the kernel (sysrq-k). This means that ps crashes as soon as it reaches acpid (without printing anything for it) and even trying to ls /proc/pid just to display the contents locks up.
acpid seems not to be working either during this - it doesn't respond to the power button, in any case.
This causes all kinds of things to go horribly wrong - start-stop-daemon can't cope..etc.
Using an otherwise identical kernel without grsecurity enabled, it doesn't do this.
I haven't got the ACL system or any sysctl-controlled options turned on at all (I have not yet configured grsecurity), which vastly limits the scope of the bug. I can't get strace to attach to acpid, I can't view its maps file, I can't really get any debugging information at all =(
I'm building a selection of kernels with different options enabled/disabled to try and localise the problem, but I'm posting this now in case anyone has any bright ideas that could save me some time =)
I'm using grsecurity 1.9.7 and Debian's 2.4.19 source.
Followup will come once I've experimented more..
Torne