On Thu, 4 Jan 2007, chas williams - CONTRACTOR wrote:
In message <[EMAIL PROTECTED]>,Derrick J Brashear writes:
Right now when we track a locker we track:
#if defined(AFS_SUN5_ENV) || defined(AFS_OBSD_ENV)
#define MyPidxx (curproc->p_pid)
...
However, my suspicion is that the cause of RT #36655 is that another
thread in the same pid now has the lock... and we're not tracking that.
Any of you poking at Solaris now have thoughts as to what we want to track
here?
just a wild guess, but kthread_t has a member:
kt_did_t t_did; /* thread id for kernel debuggers */
so perhaps curthread->t_did?
Tom Keiser suggested t_tid.
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
