linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Mathy Vanhoef <vanhoefm@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	ath5k-devel@lists.ath5k.org
Subject: Re: [PATCH 2/2] ath5k: capture CCK and OFDM restarts
Date: Sat, 14 Jun 2014 00:07:53 +0200	[thread overview]
Message-ID: <539B7639.30104@openwrt.org> (raw)
In-Reply-To: <539B7019.1050801@gmail.com>

On 2014-06-13 23:41, Mathy Vanhoef wrote:
> Hi all,
> 
> This patch allows users to see CCK and OFDM restarts when FIF_FCSFAIL is set.
> Without this patch only the stronger frame (causing the restart) would be
> visible.
> 
> The patch has been tested using our reactive jammer. The prefix of the weaker
> frame is being correctly passed on as a frame with bad CRC!
> --
> From: "Mathy Vanhoef" <vanhoefm@gmail.com>
> 
> Treat frames that underwent a CCK or OFDM restart as frames with an invalid CRC.
> 
> Signed-off-by: Mathy Vanhoef <vanhoefm@gmail.com>
> ---
>  drivers/net/wireless/ath/ath5k/base.c | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/wireless/ath/ath5k/base.c b/drivers/net/wireless/ath/ath5k/base.c
> index 39ba642..1bbc850 100644
> --- a/drivers/net/wireless/ath/ath5k/base.c
> +++ b/drivers/net/wireless/ath/ath5k/base.c
> @@ -1462,7 +1462,19 @@ ath5k_receive_frame_ok(struct ath5k_hw *ah, struct ath5k_rx_status *rs)
>  			ah->stats.rxerr_phy++;
>  			if (rs->rs_phyerr > 0 && rs->rs_phyerr < 32)
>  				ah->stats.rxerr_phy_code[rs->rs_phyerr]++;
> -			return false;
> +
> +			/*
> +			 * Threat packets that underwent a CCK of OFDM reset as having a bad CRC.
> +			 * These restarts happen when the radio resynchronizes to a stronger frame
> +			 * while receiving a weaker frame. Here we receive the prefix of the weak
> +			 * frame. Since these are incomplete packets, mark their CRC as invalid.
> +			 */
> +			if (rs->rs_phyerr == AR5K_RX_PHY_ERROR_OFDM_RESTART ||
> +			    rs->rs_phyerr == AR5K_RX_PHY_ERROR_CCK_RESTART) {
> +				rs->rs_status |= AR5K_RXERR_CRC;
> +				rs->rs_status &= (~AR5K_RXERR_PHY);
Unnecessary braces

> +			}
What about the return statement you removed, shouldn't you add that back
for the 'else' case?

- Felix

  reply	other threads:[~2014-06-13 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 21:41 [PATCH 2/2] ath5k: capture CCK and OFDM restarts Mathy Vanhoef
2014-06-13 22:07 ` Felix Fietkau [this message]
2014-06-13 23:14   ` Mathy Vanhoef
2014-06-14  0:27     ` [ath5k-devel] " Gus Wirth
2014-06-23 21:20       ` Mathy Vanhoef
2014-06-25 19:09         ` John W. Linville

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=539B7639.30104@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=ath5k-devel@lists.ath5k.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@do-not-panic.com \
    --cc=mickflemm@gmail.com \
    --cc=vanhoefm@gmail.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 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).