linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/3] mac80211: protect ->scanning by mutex in ieee80211_work_work()
Date: Fri, 16 Mar 2012 14:16:45 +0100	[thread overview]
Message-ID: <20120316131644.GB10844@redhat.com> (raw)
In-Reply-To: <1331902453.6753.4.camel@jlt3.sipsolutions.net>

On Fri, Mar 16, 2012 at 01:54:13PM +0100, Johannes Berg wrote:
> I don't really see the point in this. It seems that this doesn't really
> help, you'd actually have to protect all the work stuff here with the
> mutex so the scanning can also be excluded or so?

You mean some other work stuff than ieee80211_work_work() ?

We have almost all ieee80211_work_work() code protected by local->mtx
already, I just moved local->scanning check after the mutex_lock.

Stanislaw

  reply	other threads:[~2012-03-16 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 12:02 [RFC 1/3] mac80211: do not scan and monitor connection in parallel Stanislaw Gruszka
2012-03-16 12:02 ` [RFC 2/3] mac80211: protect ->scanning by mutex in ieee80211_work_work() Stanislaw Gruszka
2012-03-16 12:54   ` Johannes Berg
2012-03-16 13:16     ` Stanislaw Gruszka [this message]
2012-03-16 13:38       ` Johannes Berg
2012-03-16 12:02 ` [RFC 3/3] mac80211: synchronize channel switch and scan Stanislaw Gruszka
2012-03-16 12:52 ` [RFC 1/3] mac80211: do not scan and monitor connection in parallel Johannes Berg
2012-03-16 13:13   ` Stanislaw Gruszka
2012-03-16 13:21     ` Johannes Berg

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=20120316131644.GB10844@redhat.com \
    --to=sgruszka@redhat.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).