grsecurity 1.9.8 bug

[fc]

Hi,

I have 2 machines running a linux 2.4.20 kernel and ntpd. The ntp configuration is the same on the two hosts.

On one machine, the kernel is compiled with grsecurity 1.9.8. The first time I start ntpd, it starts fine. But if I stop it and restart it, it fails with "Text file busy". I need to change the inode of the ntpd binary to solve the problem (which is the kernel thinks the file is still opened). This problem doesn't occur on the host without grsecurity and didn't occur with older version of grsecurity.

So I think the problem may be related to grsecurity 1.9.8.
There's another report of the same problem (with busybox) at http://uclibc.org/lists/uclibc/2003-January.txt

[ether]

I'm using grsec 1.9.8 with kernel 2.4.20. ntpd is working fine on my machine. Here is my ACL statement for ntpd:

/usr/local/bin/ntpd {
/etc/ntp rw
/dev/log rw
}


Hope this will help!

-Michael

[PaX Team]

On one machine, the kernel is compiled with grsecurity 1.9.8. The first time I start ntpd, it starts fine. But if I stop it and restart it, it fails with "Text file busy".

there was a bug in PaX in 1.9.8-rc2 that would cause this problem but it was fixed in 1.9.8. can you double check that you're not running -rc2 accidentally?