mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	Zdenek Kabelac <zdenek.kabelac@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: INFO: possible circular locking dependency at  cleanup_workqueue_thread
Date: Wed, 20 May 2009 10:45:03 +0200	[thread overview]
Message-ID: <1242809103.19216.2.camel@johannes.local> (raw)
In-Reply-To: <d82e647a0905200121m6aa68fdcq74cd2825f43b056b@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]

On Wed, 2009-05-20 at 16:21 +0800, Ming Lei wrote:

> For me, the real puzzle is that  how lockdep introduce  #3
> (dpm_list_mtx){+.+.+.}
> 
> -> #3 (dpm_list_mtx){+.+.+.}:
>       [<ffffffff80271a64>] __lock_acquire+0xc64/0x10a0
>       [<ffffffff80271f38>] lock_acquire+0x98/0x140
>       [<ffffffff8054e78c>] __mutex_lock_common+0x4c/0x3b0
>       [<ffffffff8054ebf6>] mutex_lock_nested+0x46/0x60
>       [<ffffffff804532ff>] device_pm_add+0x1f/0xe0
>       [<ffffffff8044b9bf>] device_add+0x45f/0x570
>       [<ffffffffa007c578>] wiphy_register+0x158/0x280 [cfg80211]
>       [<ffffffffa017567c>] ieee80211_register_hw+0xbc/0x410 [mac80211]
>       [<ffffffffa01f7c5c>] iwl3945_pci_probe+0xa1c/0x1080 [iwl3945]
>       [<ffffffff803c4307>] local_pci_probe+0x17/0x20
>       [<ffffffff803c5458>] pci_device_probe+0x88/0xb0
>       [<ffffffff8044e1e9>] driver_probe_device+0x89/0x180
>       [<ffffffff8044e37b>] __driver_attach+0x9b/0xa0
>       [<ffffffff8044d67c>] bus_for_each_dev+0x6c/0xa0
>       [<ffffffff8044e03e>] driver_attach+0x1e/0x20
>       [<ffffffff8044d955>] bus_add_driver+0xd5/0x290
>       [<ffffffff8044e668>] driver_register+0x78/0x140
>       [<ffffffff803c56f6>] __pci_register_driver+0x66/0xe0
>       [<ffffffffa00bd05c>] 0xffffffffa00bd05c
>       [<ffffffff8020904f>] do_one_initcall+0x3f/0x1c0
>       [<ffffffff8027d071>] sys_init_module+0xb1/0x200
>       [<ffffffff8020c15b>] system_call_fastpath+0x16/0x1b
>       [<ffffffffffffffff>] 0xffffffffffffffff
> 
> into the lockdep graph?  in which process context?  and what is the
> previous held lock?
> After all, there is a path ( #0,#1,#2,...,#5 ) in the directed graph
> and #3 is added by
> add_lock_to_list().

Well, as Peter explained in the other part of the thread, lockdep will
always show the first cycle it found, not the shortest. The scenario
that I outlined is actually closer to this report:
http://paste.pocoo.org/show/116240/ but not quite that either, I further
shortened it.

Anyway, I have no idea how to fix it.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2009-05-20  8:46 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12  7:59 Zdenek Kabelac
2009-05-17  7:18 ` Ingo Molnar
2009-05-17 10:42   ` Ming Lei
2009-05-17 11:18   ` Johannes Berg
2009-05-17 13:10     ` Ingo Molnar
2009-05-18 19:47     ` Oleg Nesterov
2009-05-18 20:00       ` Peter Zijlstra
2009-05-18 20:16         ` Oleg Nesterov
2009-05-18 20:40           ` Peter Zijlstra
2009-05-18 22:14             ` Oleg Nesterov
2009-05-19  9:13               ` Peter Zijlstra
2009-05-19 10:49                 ` Peter Zijlstra
2009-05-19 14:53                   ` Oleg Nesterov
2009-05-19  8:51       ` Johannes Berg
2009-05-19 12:00         ` Oleg Nesterov
2009-05-19 15:33           ` Johannes Berg
2009-05-19 16:09             ` Oleg Nesterov
2009-05-19 16:27               ` Johannes Berg
2009-05-19 18:51                 ` Oleg Nesterov
2009-05-22 10:46                   ` Johannes Berg
2009-05-22 22:23                     ` Rafael J. Wysocki
2009-05-23  8:21                       ` Johannes Berg
2009-05-23 23:20                         ` Rafael J. Wysocki
2009-05-24  3:29                           ` Ming Lei
2009-05-24 11:09                             ` Rafael J. Wysocki
2009-05-24 12:48                               ` Ming Lei
2009-05-24 19:09                                 ` Rafael J. Wysocki
2009-05-24 14:30                           ` Alan Stern
2009-05-24 19:06                             ` Rafael J. Wysocki
2009-05-20  3:36             ` Ming Lei
2009-05-20  6:47               ` Johannes Berg
2009-05-20  7:09                 ` Ming Lei
2009-05-20  7:12                   ` Johannes Berg
2009-05-20  8:21                     ` Ming Lei
2009-05-20  8:45                       ` Johannes Berg [this message]
2009-05-22  8:03                 ` Ming Lei
2009-05-22  8:11                   ` Johannes Berg
2009-05-20 12:18   ` Peter Zijlstra
2009-05-20 13:18     ` Oleg Nesterov
2009-05-20 13:44       ` Peter Zijlstra
2009-05-20 13:55         ` Oleg Nesterov
2009-05-20 14:12           ` Peter Zijlstra
2009-05-24 18:58 ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1242809103.19216.2.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=tom.leiming@gmail.com \
    --cc=zdenek.kabelac@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®