Sunbug 6934356: Vector.writeObject() synchronization risks serialization deadlock

[Steve Poole]

My understanding is that the necessary contribution agreements have been
completed and that Neil and myself have been officially sanctioned by IBM
and Oracle management to participate and contribute to OpenJDK.

Of course you'll have to check with your management but as far as the two
of us  are concerned we're all squared away.


Regards

Steve Poole




From:       Mike Duigou <mike.duigou at oracle.com>
To:         core-libs-dev <core-libs-dev at openjdk.java.net>
Date:       13/12/2010 18:58
Subject:    Re: Sunbug 6934356: Vector.writeObject() synchronization risks
            serialization deadlock
Sent by:    core-libs-dev-bounces at openjdk.java.net




On Dec 13 2010, at 09:59 , Neil Richards wrote:

> Hello.
>
> I have a fix and testcase for problem 6934356 in the Java bug database
> - "Vector.writeObject() synchronization risks serialization deadlock".
> I've included the 'hg diff -g' output below.

To incorporate any fix it's necessary to have an SCA (Source Contributor
Agreement) in place. I am unsure of the status of things with IBM joining
OpenJDK and whether there's a blanket SCA for all IBM contributions in
place yet. Additionally confirmation would be needed that you are an IBM
employee (mail from an IBM domain) and authorized to contribute to OpenJDK.


Contact me directly if you need assistance sorting out the contributing
rights.

> I'm new to OpenJDK - though not to Java SE implementation development
> - so hope that this is correct mailing list to ask for the code to be
> reviewed.

This is the place!

> Also, given that this is a reported bug in the Java bug database, I'm
> a little confused as to whether I need to additionally raise it in
> https://bugs.openjdk.java.net/

This should be sufficient.

> And, indeed, whether it is better for me to include the 'hg diff -g'
> output inline, as I have done below, or as an attachment, or in some
> other fashion.

In this case the patch appears to have arrived intact. There is always some
risk of mangling by the mail list software or intermediate mail agents and
clients which is generally why patches are included as attachments.

Mike