From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Linux Wireless List" <linux-wireless@vger.kernel.org>,
"Piotr Haber" <phaber@broadcom.com>
Subject: Re: [PATCH v3.7] brcmsmac: handle packet drop on enqueuing correctly
Date: Mon, 26 Nov 2012 21:57:07 +0100 [thread overview]
Message-ID: <50B3D7A3.2000107@broadcom.com> (raw)
In-Reply-To: <20121126145511.GD4556@thinkpad-t410>
On 11/26/2012 03:55 PM, Seth Forshee wrote:
> On Fri, Nov 23, 2012 at 12:44:42PM +0100, Arend van Spriel wrote:
>> From: Piotr Haber <phaber@broadcom.com>
>>
>> In the event that tx packet can not be queued by the driver
>> the packet is dropped. Propagate that information to the .tx()
>> callback to make sure the freed packet is not accessed after
>> that.
>>
>> This has happened causing slab corruptions as reported by
>> Stanislaw Gruszka.
>>
>> Bug #47721: https://bugzilla.kernel.org/show_bug.cgi?id=47721
>>
>> Reported-by: Stanislaw Gruszka <stf_xl@wp.pl>
>> Reviewed-by: Arend van Spriel <arend@broadcom.com>
>> Reviewed-by: Pieter-Paul Giesberts <pieterpg@broadcom.com>
>> Signed-off-by: Piotr Haber <phaber@broadcom.com>
>> Signed-off-by: Arend van Spriel <arend@broadcom.com>
>> ---
>> Fixing a kernel bug so based on the wireless repository. The
>> fix for wireless-next will be posted separately as the patches
>> differ. So this patch does not need to be merged to the
>> wireless-next tree.
>
> Let me know if I can be of help in resolving the conflicts. Fwiw the fix
> looks like it ought to be easy to make on top of wireless-next, but I do
> have a couple of comments.
I have fix for wireless-next available already. Will post it later today.
>> diff --git a/drivers/net/wireless/brcm80211/brcmsmac/ampdu.c b/drivers/net/wireless/brcm80211/brcmsmac/ampdu.c
>> index be5bcfb..a6605b1 100644
>> --- a/drivers/net/wireless/brcm80211/brcmsmac/ampdu.c
>> +++ b/drivers/net/wireless/brcm80211/brcmsmac/ampdu.c
>> @@ -901,7 +901,7 @@ brcms_c_ampdu_dotxstatus_complete(struct ampdu_info *ampdu, struct scb *scb,
>> struct ieee80211_hdr *h;
>> u16 seq, start_seq = 0, bindex, index, mcl;
>> u8 mcs = 0;
>> - bool ba_recd = false, ack_recd = false;
>> + bool ba_recd = false, ack_recd = false, last_packet = false;
>> u8 suc_mpdu = 0, tot_mpdu = 0;
>> uint supr_status;
>> bool update_rate = true, retry = true, tx_error = false;
>> @@ -1010,6 +1010,8 @@ brcms_c_ampdu_dotxstatus_complete(struct ampdu_info *ampdu, struct scb *scb,
>>
>> index = TX_SEQ_TO_INDEX(seq);
>> ack_recd = false;
>> + last_packet = (((mcl & TXC_AMPDU_MASK) >> TXC_AMPDU_SHIFT) ==
>> + TXC_AMPDU_LAST);
>> if (ba_recd) {
>> bindex = MODSUB_POW2(seq, start_seq, SEQNUM_MAX);
>> BCMMSG(wiphy,
>> @@ -1074,8 +1076,7 @@ brcms_c_ampdu_dotxstatus_complete(struct ampdu_info *ampdu, struct scb *scb,
>> tot_mpdu++;
>>
>> /* break out if last packet of ampdu */
>> - if (((mcl & TXC_AMPDU_MASK) >> TXC_AMPDU_SHIFT) ==
>> - TXC_AMPDU_LAST)
>> + if (last_packet)
>> break;
>>
>> p = dma_getnexttxp(wlc->hw->di[queue], DMA_RANGE_TRANSMITTED);
>
> These changes are effectively a no-op and don't really seem to have
> anything to do with fixing the bug.
Agree. I noticed that as well and was in doubt whether I should keep it
or not. The commit message does not cover this so I resubmit the patch
(already did).
>> @@ -7288,10 +7290,12 @@ void brcms_c_sendpkt_mac80211(struct brcms_c_info *wlc, struct sk_buff *sdu,
>> prio = ieee80211_is_data(d11_header->frame_control) ? sdu->priority :
>> MAXPRIO;
>> fifo = prio2fifo[prio];
>> - if (brcms_c_d11hdrs_mac80211(wlc, hw, sdu, scb, 0, 1, fifo, 0))
>> - return;
>> - brcms_c_txq_enq(wlc, scb, sdu, BRCMS_PRIO_TO_PREC(prio));
>> + brcms_c_d11hdrs_mac80211(wlc, hw, sdu, scb, 0, 1, fifo, 0);
>
> Maybe brcms_c_d11hdrs_mac80211() should return void? I've never
> understood what its return value was supposed to represent.
All code patch in the function return 0 so it could be made void.
Gr. AvS
prev parent reply other threads:[~2012-11-26 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 11:44 [PATCH v3.7] brcmsmac: handle packet drop on enqueuing correctly Arend van Spriel
2012-11-26 14:55 ` Seth Forshee
2012-11-26 19:20 ` John W. Linville
2012-11-26 20:23 ` Arend van Spriel
2012-11-26 20:57 ` Arend van Spriel [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=50B3D7A3.2000107@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=phaber@broadcom.com \
--cc=seth.forshee@canonical.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).