RFR: 8365526: Crash with null Symbol passed to SystemDictionary::resolve_or_null [v6]

[Coleen Phillimore]

On Wed, 26 Nov 2025 23:28:10 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

>> The vm was crashing because the constant pool couldn't find the resolution error in the ResolutionErrorEntry error field.
>> 
>> There are two uses of ResolutionErrorEntry in the ResolutionErrorTable.  The key to this table is {ConstantPool, cp-index}.   In this crash, multiple threads were racing to record nest_host_errors in the case where resolution failed.  In this case, there was already a ResolutionErrorEntry in the table for the constant pool resolution failure.  In the 'if' case of add_nest_host_error we check to see if there's already a nest_host_error assuming it's the same error, then the 'else' case was unconditionally adding a ResolutionErrorEntry with just the nest host message.  Calling HashTable::put() with this entry with just the nest host message, was overwriting the entry with the constant pool resolution error, ie. the other fields.  The crash happened in ConstantPool::throw_resolution_error() because the error field was overwritten (and leaked too).
>> 
>> Add a null check before calling ResolutionErrorEntry add entry.  Also added an assert that we only add a resolution error for nest host errors in the case of success since in the case of failure there will always already be a ResolutionErrorEntry for the failing constant pool and cp index and we don't want to overwrite that again.
>> 
>> Tested with submitted reproducer and tier1-4.
>
> Coleen Phillimore has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Update src/hotspot/share/classfile/systemDictionary.cpp
>   
>   Co-authored-by: David Holmes <62092539+dholmes-ora at users.noreply.github.com>

src/hotspot/share/classfile/systemDictionary.cpp line 1868:

> 1866:     ResolutionErrorEntry* entry = ResolutionErrorTable::find_entry(pool, which);
> 1867:     if (entry == nullptr) {
> 1868:       // Only add a new entry to the resolution error table if one hasn't been found for this 

Suggestion:

      // Only add a new entry to the resolution error table if one hasn't been found for this

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/28438#discussion_r2568717797