public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: check for existance sta before adding it
Date: Wed, 3 Jun 2009 11:36:02 -0700	[thread overview]
Message-ID: <20090603183602.GD13156@tesla> (raw)
In-Reply-To: <1244053423.22576.2.camel@johannes.local>

On Wed, Jun 03, 2009 at 11:23:43AM -0700, Johannes Berg wrote:
> On Wed, 2009-06-03 at 11:08 -0700, Luis R. Rodriguez wrote:
> > On Wed, Jun 03, 2009 at 12:00:50AM -0700, Johannes Berg wrote:
> > > On Tue, 2009-06-02 at 14:01 -0700, Luis R. Rodriguez wrote:
> > > 
> > > > Thanks, yeah I see where I was making an incorrect assumption here.
> > > > 
> > > > There still is a case here where userpsace can try to add a sta twice
> > > > and the second parameters passed would be ignored.
> > > 
> > > Don't we show that -EEXIST to userspace then? I thought we did.
> > 
> > We do, but why don't we *first* try to check for its existence?
> 
> Because that's racy -- after the check completes and before we go try to
> insert a station might have come to life. Well, it might actually be ok
> due to external factors (AP mode _only_ gets stations from userspace)
> but it seems better to not rely on that.

I see.

> What problem were you trying to solve btw?

Nothing in particular, I was just reviewing sta code path.

  Luis

      reply	other threads:[~2009-06-03 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 20:30 [PATCH] mac80211: check for existance sta before adding it Luis R. Rodriguez
2009-06-02 20:35 ` Johannes Berg
2009-06-02 21:01   ` Luis R. Rodriguez
2009-06-03  7:00     ` Johannes Berg
2009-06-03 18:08       ` Luis R. Rodriguez
2009-06-03 18:23         ` Johannes Berg
2009-06-03 18:36           ` Luis R. Rodriguez [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=20090603183602.GD13156@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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