Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8288139 JavaThread touches oop after GC barrier is detached
  3. JDK-8288497

add support for JavaThread::is_oop_safe()

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Fixed
    • P2
    • 19
    • 17, 19
    • hotspot
    • b28

    Backports

      Description

        The JavaThread::_terminated field exists for tracking a JavaThread's
        journey thru the thread exit process. The detaching of the GC barrier
        from a JavaThread during the exit process is turning out to be an
        important state change that needs visibility in order to have correctly
        functioning code. Adding JavaThread::is_oop_safe() and
        the necessary associated infrastructure provides this visibility.

        This comment change from class JavaThread:

        @@ -914,7 +915,7 @@ class JavaThread: public Thread {
          private:
           // In general a JavaThread's _terminated field transitions as follows:
           //
        - // _not_terminated => _thread_exiting => _thread_terminated
        + // _not_terminated => _thread_exiting => _thread_gc_barrier_detached => _thread_terminated

        shows where the new _thread_gc_barrier_detached value
        fits into the _terminated field transitions.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8288917 add support for JavaThread::is_oop_safe()

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8291124 add support for JavaThread::is_oop_safe()

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8291276 add support for JavaThread::is_oop_safe()

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-8286830 ~HandshakeState should not touch oops

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            Enhancement - null JDK-8289003 JavaThread::check_is_terminated() implementation should rely on Thread-SMR

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8288532 additional review changes for JDK-8286830

            • P3 - Major loss of function.
            • Resolved
            links to

            Commit Commit openjdk/jdk19/e26d3b3c

            Review Review openjdk/jdk17u-dev/1514

            Review Review openjdk/jdk19/20

            Activity

              People

                dcubed Daniel Daugherty
                dcubed Daniel Daugherty
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: