From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: Report unique remain-on-channel cookie values
Date: Fri, 28 Oct 2011 14:13:52 +0300 [thread overview]
Message-ID: <4EAA8E70.9020308@qca.qualcomm.com> (raw)
In-Reply-To: <20111027130013.GA32096@jouni.qca.qualcomm.com>
On 10/27/2011 04:00 PM, Jouni Malinen wrote:
> Even though only a single concurrent remain-on-channel operation is
> supported, there may be two pending remain-on-channel events (one to
> indicate end of a canceled operation and another to indicate start of a
> new operation). User space won't be able to distinguish these events
> unless unique cookies are used.
>
> The previous behavior resulted in wpa_supplicant getting quite
> confused about the driver's offchannel state in various sequences
> and this made the P2P state machine behave incorrectly. Use of
> more than a single remain-on-channel cookie value fixes this.
Thanks, applied.
Kalle
prev parent reply other threads:[~2011-10-28 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 13:00 [PATCH] ath6kl: Report unique remain-on-channel cookie values Jouni Malinen
2011-10-28 11:13 ` Kalle Valo [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=4EAA8E70.9020308@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=jouni@qca.qualcomm.com \
--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).