public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* libgcj/9250: runtime should only use non-visible locks
@ 2003-01-09 17:56 tromey
  0 siblings, 0 replies; only message in thread
From: tromey @ 2003-01-09 17:56 UTC (permalink / raw)
  To: gcc-gnats


>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:


^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2003-01-09 17:56 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-09 17:56 libgcj/9250: runtime should only use non-visible locks tromey

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).