All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: REGRESSION: crash in wireless-testing smoketest
Date: Tue, 7 Feb 2012 15:41:25 +0100	[thread overview]
Message-ID: <4F313815.3020107@broadcom.com> (raw)

Hi Johannes,

For the brcm80211 drivers we have nightly tests running on both internal
repo and wireless-testing. Last nights test failed for wireless-testing
and it occurred during AUTH/ASSOC. I bisected the issue to following commit:

commit 7852e36186d2a1983c215836d7e3d7b8927c930d
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Fri Jan 20 13:55:24 2012 +0100

    mac80211: remove dummy STA support

    The dummy STA support was added because I didn't
    want to change the driver API at the time. Now
    that we have state transitions triggering station
    add/remove in the driver, we only call add once a
    station reaches ASSOCIATED, so we can remove the
    dummy station stuff again.

    While at it, tighten the RX check and accept only
    port control (EAP) frames from the AP station if
    it's not associated yet -- in other cases there's
    no race.

    Signed-off-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

The brcmsmac driver does not provide a sta_remove callback. I suspect
that is causing the issue here. Can you confirm?

Gr. AvS


             reply	other threads:[~2012-02-07 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 14:41 Arend van Spriel [this message]
2012-02-07 14:59 ` REGRESSION: crash in wireless-testing smoketest Johannes Berg
2012-02-07 17:25   ` Arend van Spriel
2012-02-07 20:32     ` Johannes Berg
2012-02-08 10:02       ` Arend van Spriel
2012-02-08 13:02         ` Johannes Berg
2012-02-08 13:44           ` Arend van Spriel
2012-02-08 15:37             ` Larry Finger

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=4F313815.3020107@broadcom.com \
    --to=arend@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.