All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC/RFT] ath9k_htc: avoid scheduling while atomic on sta_rc_update
Date: Mon, 3 Feb 2014 11:39:05 +0100	[thread overview]
Message-ID: <20140203103905.GB1725@redhat.com> (raw)
In-Reply-To: <52EE0997.1060402@rempel-privat.de>

On Sun, Feb 02, 2014 at 10:02:15AM +0100, Oleksij Rempel wrote:
> Am 31.01.2014 20:38, schrieb Stanislaw Gruszka:
> > On Fri, Jan 31, 2014 at 07:24:05PM +0100, Oleksij Rempel wrote:
> >> I have different HW. How can trigger sta_rc_update?
> > 
> > Below patch should trigger it when any management frame is received
> > from know sta and print information about it. 
> 
> It seems to work,
> a least it didn't crashed. I was able to trigger it only in IBSS mode.

Looks ieee80211_rx_h_mgmt with know STA is not used for Managed mode as
frequent as I thought.

Thanks for testing! I'll post the patch shortly.
Stanislaw

WARNING: multiple messages have this Message-ID (diff)
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Oleksij Rempel <linux@rempel-privat.de>
Cc: ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] ath9k_htc: avoid scheduling while atomic on sta_rc_update
Date: Mon, 3 Feb 2014 11:39:05 +0100	[thread overview]
Message-ID: <20140203103905.GB1725@redhat.com> (raw)
In-Reply-To: <52EE0997.1060402@rempel-privat.de>

On Sun, Feb 02, 2014 at 10:02:15AM +0100, Oleksij Rempel wrote:
> Am 31.01.2014 20:38, schrieb Stanislaw Gruszka:
> > On Fri, Jan 31, 2014 at 07:24:05PM +0100, Oleksij Rempel wrote:
> >> I have different HW. How can trigger sta_rc_update?
> > 
> > Below patch should trigger it when any management frame is received
> > from know sta and print information about it. 
> 
> It seems to work,
> a least it didn't crashed. I was able to trigger it only in IBSS mode.

Looks ieee80211_rx_h_mgmt with know STA is not used for Managed mode as
frequent as I thought.

Thanks for testing! I'll post the patch shortly.
Stanislaw


  reply	other threads:[~2014-02-03 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 13:37 [ath9k-devel] [RFC/RFT] ath9k_htc: avoid scheduling while atomic on sta_rc_update Stanislaw Gruszka
2014-01-31 13:37 ` Stanislaw Gruszka
2014-01-31 18:24 ` [ath9k-devel] " Oleksij Rempel
2014-01-31 18:24   ` Oleksij Rempel
2014-01-31 19:38   ` [ath9k-devel] " Stanislaw Gruszka
2014-01-31 19:38     ` Stanislaw Gruszka
2014-02-02  9:02     ` [ath9k-devel] " Oleksij Rempel
2014-02-02  9:02       ` Oleksij Rempel
2014-02-03 10:39       ` Stanislaw Gruszka [this message]
2014-02-03 10:39         ` Stanislaw Gruszka

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=20140203103905.GB1725@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=ath9k-devel@lists.ath9k.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 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.