From: Luca Coelho <luca@coelho.fi>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
sw@simonwunderlich.de, "Otcheretianski,
Andrei" <andrei.otcheretianski@intel.com>
Subject: Re: [PATCH v5 2/3] mac80211: implement chanctx reservation
Date: Fri, 07 Mar 2014 08:48:32 +0200 [thread overview]
Message-ID: <1394174912.4192.9.camel@dubbel> (raw)
In-Reply-To: <CA+BoTQkb95xGNtVUxvn_u==P6fuy-h0iNAp8pGEcq8m0ZUm-7A@mail.gmail.com>
On Wed, 2014-03-05 at 13:04 +0100, Michal Kazior wrote:
> On 5 March 2014 12:11, Luca Coelho <luca@coelho.fi> wrote:
>
> [...]
>
> > + /* unref our reservation before assigning */
> > + ctx->refcount--;
> > + sdata->reserved_chanctx = NULL;
> > + ret = ieee80211_assign_vif_chanctx(sdata, ctx);
> > + if (ret) {
> > + /* if assign fails refcount stays the same */
> > + if (ctx->refcount == 0)
> > + ieee80211_free_chanctx(local, ctx);
> > + goto out_wake;
> > + }
>
> This actually won't work if there are AP VLANs (I noticed that yesterday).
>
> You can't call ieee80211_vif_copy_chanctx_to_vlans() here due to
> current locking requirements. I have a patch for that though ;-) I'll
> send it soon.
How is this related to this patch?
Anyway, good to know that you have fixed it. :)
--
Luca.
next prev parent reply other threads:[~2014-03-07 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 11:11 [PATCH v5 0/3] mac802111: channel context reservation Luca Coelho
2014-03-05 11:11 ` [PATCH v5 1/3] mac80211: split ieee80211_vif_change_channel in two Luca Coelho
2014-03-05 11:11 ` [PATCH v5 2/3] mac80211: implement chanctx reservation Luca Coelho
2014-03-05 12:04 ` Michal Kazior
2014-03-07 6:48 ` Luca Coelho [this message]
2014-03-10 7:03 ` Michal Kazior
2014-03-10 9:08 ` Luca Coelho
2014-03-10 9:18 ` Michal Kazior
2014-03-05 11:11 ` [PATCH v5 3/3] mac80211: allow reservation of a running chanctx Luca Coelho
2014-03-05 11:32 ` Michal Kazior
2014-03-07 6:43 ` Luca Coelho
2014-03-07 20:19 ` Joe Perches
2014-03-09 13:38 ` Luca Coelho
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=1394174912.4192.9.camel@dubbel \
--to=luca@coelho.fi \
--cc=andrei.otcheretianski@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=sw@simonwunderlich.de \
/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).