Date: Thu, 13 Feb 2014 12:53:45 -0800 From: Alfred Perlstein <bright@mu.org> To: Vijay Singh <vijju.singh@gmail.com>, hackers@freebsd.org Subject: Re: Debugging rw lock Message-ID: <52FD30D9.6050604@mu.org> In-Reply-To: <CALCNsJS6vFJU18F3VRR-T2RdtGNxd3fycUCkQ63BmGp29DAUMw@mail.gmail.com> References: <CALCNsJS6vFJU18F3VRR-T2RdtGNxd3fycUCkQ63BmGp29DAUMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Keep a stack of rwlocks owned in the struct thread.
-Alfred
On 2/13/14, 12:51 PM, Vijay Singh wrote:
> I am running into an issue where an rw lock is read locked and never
> unlocked, and causes a system to livelock. I was wondering if its possible
> to figure out which thread owns the read lock?
>
> It's the tcp pcbinfo lock.
>
> (kgdb-amd64-7.4-08) show_rwlock rw
> name : tcp
> class: rw
> flags: {SLEEP, INITED, WITNESS, RECURSE, UPGRADABLE}
> state: RLOCK: 1 locks
> waiters: writers
>
> Any help is appreciated.
>
> -vijay
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52FD30D9.6050604>