linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juuso Oikarinen <juuso.oikarinen@nokia.com>
To: ext Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC PATCHv2] mac80211: Add support for hardware ARP query filtering
Date: Thu, 27 May 2010 08:36:50 +0300	[thread overview]
Message-ID: <1274938610.5277.2914.camel@wimaxnb.nmp.nokia.com> (raw)
In-Reply-To: <1274878321.3658.7.camel@jlt3.sipsolutions.net>

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
> 



      reply	other threads:[~2010-05-27  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 11:29 [RFC PATCHv2] mac80211: Add support for hardware ARP query filtering Juuso Oikarinen
2010-05-26 11:52 ` Johannes Berg
2010-05-26 12:51   ` Juuso Oikarinen
2010-05-26 12:52     ` Johannes Berg
2010-05-27  5:36       ` Juuso Oikarinen [this message]

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=1274938610.5277.2914.camel@wimaxnb.nmp.nokia.com \
    --to=juuso.oikarinen@nokia.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).