Re: Weird coincidental PAX crashes

On 05/15/2014 09:48 AM, PaX Team wrote:
> 
> unfortunately the backtrace is not usable as is due to lack of symbols.
> if you still have the original vmlinux around (or can reproduce it with
> all the debug symbols) then i can take a look and perhaps figure out
> where the refcount overflow was detected (and whether it was a false
> positive or not).
> 
>> If it's not hardware (two different machines...), does this look like a
>> kernel bug? Should I upgrade over the weekend and pray?
> 
> it's not a hardware issue (at least not directly) but a software one and
> regardless of it being perhaps a false positive you should be using a newer
> kernel that we support ;).
> 

Thanks, I wasn't sure if it was a kernel issue at first (which is why I
posted here instead of filing a bug). But it took out a production
server in the middle of the day, and I was out of the office, so I had
to just shut-up-and-fix-it quickly.

I've since upgraded to a newer kernel and everything looks OK, but the
issue only showed up after around 5 months of uptime. If I go another 5
months without an upgrade or reboot, maybe I'll find out if the issue is
reproducible =)