From: Kalle Valo <kvalo@codeaurora.org>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: linux-wireless@vger.kernel.org, Larry.Finger@lwfinger.net,
stable@vger.kernel.org, Jes Sorensen <Jes.Sorensen@redhat.com>
Subject: Re: [1/2] rtl8xxxu: Fix memory leak in handling rxdesc16 packets
Date: Fri, 7 Oct 2016 11:22:58 +0000 (UTC) [thread overview]
Message-ID: <20161007112258.241FA61AD5@smtp.codeaurora.org> (raw)
In-Reply-To: <1475178055-16924-2-git-send-email-Jes.Sorensen@redhat.com>
Jes Sorensen <Jes.Sorensen@redhat.com> wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> A device running without RX package aggregation could return more data
> in the USB packet than the actual network packet. In this case we
> could would clone the skb but then determine that that there was no
> packet to handle and exit without freeing the cloned skb first.
>
> This has so far only been observed with 8188eu devices, but could
> affect others.
>
> Signed-off-by: Jes Sorensen <Jes.Sorensen@redhat.com>
> Cc: stable@vger.kernel.org # 4.8+
2 patches applied to wireless-drivers.git, thanks.
1e54134ccad0 rtl8xxxu: Fix memory leak in handling rxdesc16 packets
8a55698f2f29 rtl8xxxu: Fix big-endian problem reporting mactime
--
https://patchwork.kernel.org/patch/9356961/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2016-10-07 11:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 19:40 [PATCH 0/2] rtl8xxxu: Fix memory leak and big endian bug Jes.Sorensen
2016-09-29 19:40 ` [PATCH 1/2] rtl8xxxu: Fix memory leak in handling rxdesc16 packets Jes.Sorensen
2016-10-03 7:24 ` Kalle Valo
2016-10-03 7:25 ` Kalle Valo
2016-10-03 12:34 ` Jes Sorensen
2016-10-07 11:22 ` Kalle Valo [this message]
2016-09-29 19:40 ` [PATCH 2/2] rtl8xxxu: Fix big-endian problem reporting mactime Jes.Sorensen
2016-10-03 7:26 ` Kalle Valo
2016-10-03 12:34 ` Jes Sorensen
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=20161007112258.241FA61AD5@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Jes.Sorensen@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.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 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).