linux-kernel - Re: Question on lockdep and sysrq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 23 May 2009 09:03:58 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Ben Greear <greearb@...delatech.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Question on lockdep and sysrq - d

See http://marc.info/?l=linux-kernel&m=124211522525625&w=2.

thanks.

2009/5/23 Ben Greear <greearb@...delatech.com>:
> Hello!
>
> I'm trying to debug an apparent deadlock in some code I'm
> writing.
>
> When I do a sysrq 'd', I get a nice dump of locks (I have lockdep enabled).
>
> However, the output appears to show multiple processes holding the
> same locks (rtnl_mutex, for example):
>
> Showing all locks held in the system:
> 3 locks held by events/11/63:
>  #0:  (events){--..}, at: [<ffffffff8104f71e>] run_workqueue+0xb1/0x216
>  #1:  ((linkwatch_work).work){--..}, at: [<ffffffff8104f71e>]
> run_workqueue+0xb1/0x216
>  #2:  (rtnl_mutex){--..}, at: [<ffffffff8125def1>] rtnl_lock+0x12/0x14
> 1 lock held by irqbalance/3360:
>  #0:  (rtnl_mutex){--..}, at: [<ffffffff8125def1>] rtnl_lock+0x12/0x14
> 1 lock held by hald/3605:
>  #0:  (rtnl_mutex){--..}, at: [<ffffffff8125def1>] rtnl_lock+0x12/0x14
> ...
>
> Is this merely showing processes that are blocked on trying to acquire these
> locks?
>
> If so, is there any way to tell which processes have fully acquired locks
> v/s
> just waiting to acquire them?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@...delatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>



-- 
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/