From: Gabor Juhos <juhosg@openwrt.org>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH 3/3] p54: zero-out rx_status
Date: Tue, 11 Dec 2012 18:16:56 +0100 [thread overview]
Message-ID: <50C76A88.1030008@openwrt.org> (raw)
In-Reply-To: <201212111608.43293.chunkeey@googlemail.com>
2012.12.11. 16:08 keltezéssel, Christian Lamparter írta:
> On Tuesday, December 11, 2012 02:55:05 PM Gabor Juhos wrote:
>> In commit 'mac80211: support radiotap vendor namespace RX data'
>> new fields were added to 'struct ieee80211_rx_status'.
>> The ath5k driver does not initializes those fields and
> ^^^^^ p54?!
Of course.
>> this can cause unexpected behaviour. The patch ensures
>> that each field gets initialized with zeroes.
>
> Actually, when the skb is alloced/initialized by
> __alloc_skb, the skb->cb is already zeroed
Thank you for the explanation, I was not aware of this.
> (which is where the ieee80211_rx_status will be stored).
>
> And while p54 recycles command response skbs, the
> driver does not touch the skb->cb of 802.11 skbs,
> until the frame is destined for ieee80211_rx_irqsave.
Ok.
> If this issue just popped up now, I suspect that
> something else is silently corrupting our SKBs
> [or can anybody see how rt2x00 hit this issue?]
It is popped up now because we have switched to compat-wireless-2012-12-06 in
OpenWrt a few days ago. Previously we were using compat-wireless-2012-09-07.
-Gabor
prev parent reply other threads:[~2012-12-11 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 13:55 [PATCH 1/3] rt2x00: zero-out rx_status Gabor Juhos
2012-12-11 13:55 ` [PATCH 2/3] ath5k: " Gabor Juhos
2012-12-11 13:55 ` [PATCH 3/3] p54: " Gabor Juhos
2012-12-11 15:08 ` Christian Lamparter
2012-12-11 15:25 ` Johannes Berg
2012-12-11 15:30 ` Johannes Berg
2012-12-11 15:38 ` Christian Lamparter
2012-12-11 17:19 ` Gabor Juhos
2012-12-11 17:16 ` Gabor Juhos [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=50C76A88.1030008@openwrt.org \
--to=juhosg@openwrt.org \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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.