On Fri, 2011-06-03 at 22:58 +0200, Johannes Berg wrote:
> On Fri, 2011-06-03 at 17:00 +0100, duaneg@xxxxxxxxx wrote:
> > Hi there,
> >
> > I'm getting a deadlock with 3.0.0-rc1:
> >
> > Jun 3 12:06:20 kereru kernel: =======================================================
> > Jun 3 12:06:20 kereru kernel: [ INFO: possible circular locking dependency detected ]
> > Jun 3 12:06:20 kereru kernel: 3.0.0-rc1-00049-g1fa7b6a #57
> > Jun 3 12:06:20 kereru kernel: -------------------------------------------------------
> > Jun 3 12:06:20 kereru kernel: kworker/0:1/4525 is trying to acquire lock:
> > Jun 3 12:06:20 kereru kernel: (&rdev->mtx){+.+.+.}, at: [<ffffffff8164c831>] cfg80211_netdev_notifier_call+0x131/0x5b0
> > Jun 3 12:06:20 kereru kernel:
> > Jun 3 12:06:20 kereru kernel: but task is already holding lock:
> > Jun 3 12:06:20 kereru kernel: (&rdev->devlist_mtx){+.+.+.}, at: [<ffffffff8164dcef>] cfg80211_rfkill_set_block+0x4f/0xa0
> > Jun 3 12:06:20 kereru kernel:
> > Jun 3 12:06:20 kereru kernel: which lock already depends on the new lock.
>
> This is caused by Luca's scheduled scan changes. The reason is that
> cfg80211_rfkill_set_block holds devlist_mtx, but then he added
> cfg80211_lock_rdev(rdev); to NETDEV_GOING_DOWN, which is of course
> invoked by dev_close() in cfg80211_rfkill_set_block(). Thus, the
> problem. Not sure what to do to solve it, I'll let him sort it out :)
Argh! Well, I guess I have to look into how to solve this. :\
--
Cheers,
Luca.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
