Method and tool for determining ownership of a multiple owner lock in multithreading environments

• US 6,886,081 B2
• Filed: 09/17/2002
• Issued: 04/26/2005
• Est. Priority Date: 09/17/2002
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Harres, John M.
• Primary Examiner(s): Sparks, Donald
• Assistant Examiner(s): Farrokh, Hashem
• Application Number:
  US10/245,069
• Publication Number:
  US 20040054861A1
• Time in Patent Office: 952 Days
• Field of Search: 711101-105, 711/152, 711/154, 711161-163, 711144-145, 711/1, 718100-102, 718/104, 707/8, 710/8, 710/18, 710/30, 710/200, 710/244
• US Class Current: 711/152
• CPC Class Codes: G06F 9/524 Deadlock detection or avoidance

Abstract

A method for determining an ownership of for a multiple owner lock. The method includes determining potential owners of the lock by inspecting a core file of a computer system or memory of a live system to determine which threads have pointers to the lock. The method includes identifying a stack for the threads with a stack pointer pointing to the current active frame and dividing the stack into active and inactive portions. The stack information is examined for each potential owner of the lock for pointers to the lock. If the thread has a pointer to the lock in the inactive portion of the stack, the thread is removed from the set of potential owners. The method includes retrieving a waiting list for the lock, and any threads on the waiting list are removed from the set of potential owners.

Claims

1. A computer-based method for determining an owner of a lock on a shared resource in a computer system, comprising:

receiving a core file generated in the computer system providing state information for memory in the computer system including stack information for threads in the computer system; and

processing the core file for the computer system to generate a list of potential owners of the lock, wherein the lock is configured for multiple ownership with a kernel for the computer system not storing lock ownership information for the lock and wherein the potential owners are the threads in the computer system and the processing includes locating in the stack information for each owner a pointer to the lock.

2. The method of claim 1, further including prior to the processing, examining the core file to identify the lock.

3. The method of claim 1, further including identifying an inactive portion of a current stack for the computer system from the core file and removing the potential owners that have a local variable pointer in the stack information pointing to the inactive portion.

4. The method of claim 1, further including retrieving an analysis rule set for the lock, applying the retrieved analysis rule set to the threads identified in the list of potential owners of the lock, and removing the threads not complying with the analysis rule set from the list of potential owners.

5. The method of claim 1, further including examining the core file for a waiting list for the lock including an identifier for each thread waiting for ownership of the lock and removing from the list of potential owners each of the threads in the list of the potential owners that are included in the waiting list.

6. The method of claim 5, wherein the lock is a read/write lock or a semaphore.

7. The method of claim 1, further including generating a report including the list of potential owners of the lock.

8. A method of determining prior ownership in a computer system of a lock to a resource shared by threads of execution, comprising:

retrieving a set of the threads identified as potential prior owners of the lock;

identifying a stack for the each of the identified threads that is maintained by a processor in the computer system;

determining an active and an inactive portion of each of the thread stacks based on a stack pointer; and

for each of the threads, identifying a location in the thread stack of a pointer to the lock;

determining for each of the threads whether the location of the pointer to the lock is in the active or the inactive portion of the thread stack; and

removing the threads in the set that have the pointer to the lock in the inactive portion of the thread stack.

9. The method of claim 8, further including retrieving a sleep queue for the lock listing threads waiting for ownership of the lock and removing any of the threads in the set that are listed in the sleep queue for the lock.

10. The method of claim 8, further including generating the set of the potential owner threads by determining for each of the threads in the computer system whether the thread has a pointer to the lock in the stack maintained for the thread.

11. The method of claim 8, further including receiving a core file for the computer system and processing the core file to locate the lock for which ownership is to be determined.

12. A computer-based method for determining lock ownership in a multithreading operating system, comprising:

retrieving a core file for a computer system;

processing the core file to create a set of threads of execution determined to be potential owners of a lock to a resource shared by the threads;

locating a waiting list for ownership to the lock including threads waiting to own the lock; and

removing all of the waiting threads from the set of potential owner threads.

13. The method of claim 12, further including identifying stack information for each of the threads in the set including a pointer to the lock, determining for each of the threads whether the pointer to the lock is in an inactive portion of a stack for the thread, and removing the threads having the pointers determined located in the inactive portions of the stacks from the set of potential owner threads.

14. The method of claim 13, wherein the lock is a read/write lock or a semaphore.

15. The method of claim 13, further including generating a report including the set of potential owner threads.

16. The method of claim 12, further wherein the determination of the potential owner threads in the processing includes locating threads of execution in the operating system having a pointer to the lock.

17. A computer readable medium, comprising:

computer readable program code devices configured to cause a computer to effect generating a set of potential owners of a lock to a system resource including threads of execution determined to have a pointer to the lock, wherein the lock is configured for multiple ownership and a kernel associated with the lock does not store lock ownership information for the lock;

computer readable program code devices configured to cause a computer to effect retrieving a set of threads waiting for ownership of the lock; and

computer readable program code devices configured to cause a computer to effect removing any of the waiting threads from the set of potential owner threads.

18. The computer readable medium of claim 17, further including computer readable program code devices configured to cause a computer to effect removing the threads in the set of potential owner threads having a pointer to the lock in the inactive portion of the stack for the thread.

19. The computer readable medium of claim 17, further including computer readable program code devices configured to cause a computer to effect identifying the lock from by processing a core file to identify an active lock as a cause of a panic.

20. The computer readable medium of claim 17, wherein the lock is a read/write lock or a semaphore.