Page 1 of 1
2.1.12-2.6.25.9-200806300858 doesn't seem to log signals
Posted:
Thu Jul 03, 2008 3:18 amby szo
See subject, I was playing around with a the new test patch and I noticed that the signals are not logged for some reason.
Re: 2.1.12-2.6.25.9-200806300858 doesn't seem to log signals
Posted:
Thu Jul 03, 2008 5:17 pmby spender
It's working fine for me here. So I have to ask some dumb questions: is CONFIG_GRKERNSEC_SIGNAL enabled in your compiled kernel? What's your test case?
-Brad
Re: 2.1.12-2.6.25.9-200806300858 doesn't seem to log signals
Posted:
Fri Jul 04, 2008 3:25 amby szo
It is on, I double-checked.
The test case is kill -11 pid-of-my-other-shell
then dmesg show nothing new. Other things like (u)mount are logged fine.
Re: 2.1.12-2.6.25.9-200806300858 doesn't seem to log signals
Posted:
Sat Jul 05, 2008 6:19 pmby spender
Thanks for the report. What was the last kernel you used where you test case worked properly? I've fixed the problem in the current test patch. Forced signals (from an application crashing) were logged properly, but signals sent by a user to a process weren't logged.
-Brad
Re: 2.1.12-2.6.25.9-200806300858 doesn't seem to log signals
Posted:
Mon Jul 07, 2008 4:43 amby szo
I don't think I can help you pinpoint the introduction of the bug, the current kernel running is 2.4.32
