On Wed, 2010-05-26 at 14:52 +0200, ext Johannes Berg wrote: > On Wed, 2010-05-26 at 15:51 +0300, Juuso Oikarinen wrote: > > > > > + rtnl_lock(); > > > > + ieee80211_set_arp_filter(sdata); > > > > + rtnl_unlock(); > > > > + > > > > > > Please analyse locking in more detail and enable lockdep :) > > > > > > This will cause deadlocks. > > > > I have lockdep permanently enabled in my development kernel. It has > > given me no complaints in testing with the corresponding wl1271 driver > > patch. > > > > But I will look into those locks further if I can figure out any > > deadlock scenarios. > > Interesting .. because for sure a lot of the ieee80211_mgd_* functions > are called with rtnl held and lock the mgd mutex, but it is the other > way around here. You are right. There are at least some paths where mgd mutex is locked with rtnl held, so there is a risk of deadlock. This has not occurred in my limited testing, but is certainly possible, and obviously we should always do locking in the same order. I'll have to see if I can move this notification outside the mgd lock, and if I can't, I'll have to use a workqueue function. -Juuso > johannes > -- 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
