linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: <kvalo@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: Inform bss information to cfg80211 before connect event
Date: Fri, 2 Dec 2011 16:17:11 +0530	[thread overview]
Message-ID: <20111202104709.GB28660@chvasanth-lnx> (raw)
In-Reply-To: <1322818619-29265-1-git-send-email-vthiagar@qca.qualcomm.com>

On Fri, Dec 02, 2011 at 03:06:59PM +0530, Vasanthakumar Thiagarajan wrote:
> This is already done but only when bss entry is not availabe
> or aged out. Not updating the bss information when that bss
> is available creates a case where there is a bss entry when
> checked in ath6kl_cfg80211_connect_event() but it got aged out
> by the time cfg80211 checks for the bss entry in __cfg80211_roamed().
> This results in the following warning and the failure to notify
> roaming event to application. To fix this, update the bss information
> for which a romaing event is received. Also renamed ath6kl_add_bss_if_needed()
> to ath6kl_inform_bss().
> 
> [158645.538384] WARNING: at net/wireless/sme.c:586
> __cfg80211_roamed+0xc2/0x1b1()
> [158645.538810] Call Trace:
> [158645.538838]  [<c1033527>] warn_slowpath_common+0x65/0x7a
> [158645.538917]  [<c14cfacf>] ? __cfg80211_roamed+0xc2/0x1b1
> [158645.538946]  [<c103354b>] warn_slowpath_null+0xf/0x13
> [158645.539055]  [<c14cfacf>] __cfg80211_roamed+0xc2/0x1b1
> [158645.539086]  [<c14beb5b>] cfg80211_process_rdev_events+0x153/0x1cc
> [158645.539166]  [<c14bd57b>] cfg80211_event_work+0x26/0x36
> [158645.539195]  [<c10482ae>] process_one_work+0x219/0x38b
> [158645.539273]  [<c14bd555>] ? wiphy_new+0x419/0x419
> [158645.539301]  [<c10486cb>] worker_thread+0xf6/0x1bf
> [158645.539379]  [<c10485d5>] ? rescuer_thread+0x1b5/0x1b5
> [158645.539407]  [<c104b3e2>] kthread+0x62/0x67
> [158645.539484]  [<c104b380>] ? __init_kthread_worker+0x42/0x42
> [158645.539514]  [<c151309a>] kernel_thread_helper+0x6/0xd
> 
> Reported-by: Kalle Valo <kvalo@qca.qualcomm.com>
> Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>

Please drop this patch, this needs more work.

Vasanth

  reply	other threads:[~2011-12-02 10:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  9:36 [PATCH] ath6kl: Inform bss information to cfg80211 before connect event Vasanthakumar Thiagarajan
2011-12-02 10:47 ` Vasanthakumar Thiagarajan [this message]
2011-12-02 11:48 ` Jouni Malinen
2011-12-02 11:52   ` Kalle Valo
2011-12-05  9:36   ` Vasanthakumar Thiagarajan

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=20111202104709.GB28660@chvasanth-lnx \
    --to=vthiagar@qca.qualcomm.com \
    --cc=kvalo@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).