From: Bob Copeland <me@bobcopeland.com>
To: "fengwei.yin" <fengwei.yin@linaro.org>
Cc: linux-wireless@vger.kernel.org, wcn36xx@lists.infradead.org,
k.eugene.e@gmail.com, bjorn.andersson@sonymobile.com,
lking@qti.qualcomm.com
Subject: Re: [PATCH] wcn36xx: handle rx skb allocation failure to avoid system crash
Date: Fri, 11 Dec 2015 08:37:30 -0500 [thread overview]
Message-ID: <20151211133730.GA8835@localhost> (raw)
In-Reply-To: <566ACC1C.1070304@linaro.org>
On Fri, Dec 11, 2015 at 09:14:04PM +0800, fengwei.yin wrote:
>
> On 2015/12/2 13:27, Fengwei Yin wrote:
> >Lawrence reported that git clone could make system crash on a
> >Qualcomm ARM soc based device (DragonBoard, 1G memory without
> >swap) running 64bit Debian.
> >
> >It's turned out the crash is related with rx skb allocation
> >failure. git could consume more than 600MB anonymous memory.
> >And system is in extremely memory shortage case.
> >
> >But driver didn't handle the rx allocation failure case. This patch
> >doesn't submit skb to upper layer if rx skb allocation fails.
> >Instead, it reuse the old skb for rx DMA again. It's more like
> >drop the packets if system is in memory shortage case.
> >
> >With this change, git clone is OOMed instead of system crash.
> >
> >Reported-by: King, Lawrence <lking@qti.qualcomm.com>
> >Signed-off-by: Fengwei Yin <fengwei.yin@linaro.org>
Concept makes sense to me, but:
> > dma_addr = dxe->dst_addr_l;
> >- wcn36xx_dxe_fill_skb(wcn->dev, ctl);
> >+ ret = wcn36xx_dxe_fill_skb(wcn->dev, ctl);
> >+ if (0 == ret) {
I find this "success handling" to be unclear and traditionally this
kind of thing is a source of bugs; how about instead:
> >+ /* new skb allocation ok. Use the new one and queue
> >+ * the old one to network system.
> >+ */
> >+ dma_unmap_single(wcn->dev, dma_addr, WCN36XX_PKT_SIZE,
> >+ DMA_FROM_DEVICE);
> >+ wcn36xx_rx_skb(wcn, skb);
> >+ }
ret = wcn36xx_dxe_fill_skb(wcn->dev, ctl);
/* skip this frame if we can't alloc a new rx buffer */
if (ret)
goto drop;
> > switch (ch->ch_type) {
> > case WCN36XX_DXE_CH_RX_L:
> >@@ -495,9 +504,6 @@ static int wcn36xx_rx_handle_packets(struct wcn36xx *wcn,
> > wcn36xx_warn("Unknown channel\n");
> > }
> >
> >- dma_unmap_single(wcn->dev, dma_addr, WCN36XX_PKT_SIZE,
> >- DMA_FROM_DEVICE);
> >- wcn36xx_rx_skb(wcn, skb);
drop:
> > ctl = ctl->next;
> > dxe = ctl->desc;
> > }
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2015-12-11 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 5:27 [PATCH] wcn36xx: handle rx skb allocation failure to avoid system crash Fengwei Yin
2015-12-11 13:14 ` fengwei.yin
2015-12-11 13:37 ` Bob Copeland [this message]
2015-12-11 13:44 ` fengwei.yin
2015-12-11 14:08 ` Bob Copeland
2015-12-12 1:12 ` fengwei.yin
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=20151211133730.GA8835@localhost \
--to=me@bobcopeland.com \
--cc=bjorn.andersson@sonymobile.com \
--cc=fengwei.yin@linaro.org \
--cc=k.eugene.e@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lking@qti.qualcomm.com \
--cc=wcn36xx@lists.infradead.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.