grsecurity forums

Hi,

Kernel panic on my server used for shared virtual hosting. I use vanilla 3.14.11 kernel and grsecurity-3.0-3.14.11-201407081919.patch
crashdump https://www.dropbox.com/s/3kewmqxxtoj8a ... 1.txt?dl=0

1. Kernel config https://www.dropbox.com/s/2bifr4yk1tqna ... 1.txt?dl=0

2. # ld --version
GNU ld (GNU Binutils) 2.23.2
Copyright 2012 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

3. vmlinux https://www.dropbox.com/s/spy7xciqdo9ov ... 14.11?dl=0

4. BzImage https://www.dropbox.com/s/qa9yvoxr4u1uc ... 14.11?dl=0

5. System.map https://www.dropbox.com/s/lermuxdqe97ph ... 14.11?dl=0

first of all, this is a rather old kernel, can you try something more recent? also how reproducible is this lockup? i take it that it's not often if it just happened after half a year . in general, we don't touch sem locking code at all, so i wonder if it's a vanilla bug or perhaps you had some other issues earlier. can you check your kernel logs for any oops/warnings/etc before this lockup was detected?