grsecurity forums

I'm using a 2.4.19-gentoo-r7 kernel patched with grsecurity and Medium security level.
I'm having this problems with mysql-3.23.51:

Code: Select all

020704 03:27:26  mysqld started
mysqld got signal 11;
[...]

Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Bogus stack limit or frame pointer, fp=0xbff58608, stack_bottom=0x605fd510, thread_stack=131072, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x5f94ce10  is invalid pointer
thd->thread_id=1752394094

Successfully dumped variables, if you ran with --log, take a look at the details of what thread 1752394094 did to cause the crash.  In some cases of really bad corruption, the values shown above may be invalid


and my kernel logs for grsecurity show this:

Code: Select all

Jul  4 03:27:26 s0 grsec: signal 11  sent to (mysqld:547) UID(60) EUID(60), parent (safe_mysqld:14515) UID(0) EUID(0)


that's a bug in MySQL. grsecurity is only letting you know that mysql caused a segmentation fault (signal 11). It wasn't grsecurity that send the signal, but rather caused by a bug in the MySQL code.

-Brad