RFR 8004124: Handle and/or warn about SI_KERNEL

Coleen Phillimore coleen.phillimore at oracle.com
Thu Jun 20 14:20:02 PDT 2013

Thanks!   I'm using AMD64 as conditional because that's what the rest of 
the signal handler uses.

On 06/20/2013 05:23 PM, Mikael Gerdin wrote:
> Coleen,
> On 06/20/2013 11:08 PM, Coleen Phillimore wrote:
>> This wiki page refers to 64 bit addresses and we've mostly seen this
>> SI_KERNEL linux bug on 32 bit platforms.  I can't remember if we've ever
>> seen it on 64 bit platforms.  If I exclude LP64 would you review this
>> change?
>> thanks,
>> Coleen
> That's fine with me.
> Ship it!
> /Mikael
>> On 06/20/2013 04:27 PM, Mikael Gerdin wrote:
>>> Coleen,
>>> On 06/20/2013 04:48 PM, Coleen Phillimore wrote:
>>>> Summary: Detect this crash in the signal handler and give a fatal 
>>>> error
>>>> message  instead of making us chase down bugs that don't reproduce
>>>> This change also has more information for crash site from bug
>>>> https://jbs.oracle.com/bugs/browse/JDK-8007019
>>>> guarantee(cb->is_adapter_blob() || 
>>>> cb->is_method_handles_adapter_blob())
>>>> failed: exception happened outside interpreter, nmethods and vtable
>>>> stubs (1) <https://jbs.oracle.com/bugs/browse/JDK-8007019>
>>>> There used to be two places that had the same message so they were
>>>> qualified by (1) and (2).   The second one is gone.   Now this prints
>>>> the blob and pc.
>>>> Tested with full vm.quick.testlist and the sets of jdi tests that 
>>>> failed
>>>> with -client -Xcomp and specjvm98 that used to fail with this signal
>>>> code.   I got one failure two days ago before this change but now it
>>>> won't fail with my new message or at all.
>>> The error message you added for SI_KERNEL puts the blame
>>> unconditionally on the kernel.
>>> As I mentioned in the bug it's possible to cause this signal
>>> combination by trying to access memory with an invalid memory address
>>> on non-canonical form:
>>> https://en.wikipedia.org/wiki/X86-64#Canonical_form_addresses
>>> (sorry for the wikipedia link, I don't have the Intel X86_64 manual
>>> page reference at hand)
>>> Basically, if we trash an object somewhere or the compiler does
>>> something strange we may try to use a random value from memory as an
>>> address and if that address is on non-canonical form we'll say that
>>> the OS is broken when in fact it is probably our fault.
>>> /Mikael
>>>> open webrev at http://cr.openjdk.java.net/~coleenp/8004124/
>>>> bug link at http://bugs.sun.com/view_bug.do?bug_id=8004124
>>>> local bug link https://jbs.oracle.com/bugs/browse/JDK-8004124
>>>> Thanks,
>>>> Coleen

More information about the hotspot-runtime-dev mailing list