[grsec] Problem with 2.4.33.3 and grsec 2.1.9

[Torbjörn Svensson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello!

I have been running grsec enabled kernels (almost the "high" level) for
a long time and haven't much of any issue with it, but this weekend my
server just rebooted by itself. I weren't at home, and the power didn't
get disconnected as my other hosts on the same UPS still got power.

I am suspecting a bug in that kernel or in that version of grsec and/or
a combination. This is the only thing I have changed on that host for
the last month. The strange thing is that _nothing_ got logged. The last
message I have seen, before the restart, in my logs were:
Sep 10 14:41:27 localhost fetchmail[28368]: sleeping at Sun Sep 10
14:41:27 2006
Sep 10 14:43:59 localhost syslogd 1.4.1#17: restart.


A few weeks ago, a friend told me that one of his servers also got
rebooted, and that server was also running a 2.4.33.x kernel with grsec.


So, my real questions is, are there any known problems with latest 2.4
with grsec? Are there going to be any grsec-patches that will work with
any of the pre/rc packages of 2.4.34? If so, I could test one of those
and see if it reboots with that one too, but the patches for 2.4.33.x
won't apply cleanly (some ASM file has changed).


Thanks for the great job you guys puts in this!


Kind regards,
- --
  .''`. Torbjörn Svensson, azoff (at) se (dot) linux (dot) org
 : :' : 7EB9 2DC5 61AE DAB5 7099  BAC6 798E E39A DBDB 0CFD
 `. `'  http://www.azoff.se | http://dev.azoff.se
   `--  http://se.linux.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFBb2EeY7jmtvbDP0RApj3AKC73SIvOjrvPucj7m1tl7zDwwVHtgCfboii
X01jrVuMQ19OIVgMfnbq/HA=
=E9lr
-----END PGP SIGNATURE-----