libgcj/9250: runtime should only use non-visible locks

[tromey@redhat.com]

>Number:         9250
>Category:       libgcj
>Synopsis:       runtime should only use non-visible locks
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 09 09:56:02 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
Currently some parts of the runtime use user-visible
locks.  For instance, we acquire a lock on Class.class
before doing certain synchronized class operations.
This is a bug because malicious user code (e.g., an applet)
can acquire this lock and prevent the runtime from
functioning properly.  Instead in these cases we should
have a new lock that is not visible and use it.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: