From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Stable <stable@vger.kernel.org>,
Eric Biggers <ebiggers3@gmail.com>
Subject: Re: [PATCH 23/23 V2 for 3.19] rtlwifi: Fix error when accessing unmapped memory in skb
Date: Sun, 28 Dec 2014 07:50:31 +0200 [thread overview]
Message-ID: <87a928726w.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1419711457-21469-1-git-send-email-Larry.Finger@lwfinger.net> (Larry Finger's message of "Sat, 27 Dec 2014 14:17:37 -0600")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> These drivers use 9100-byte receive buffers, thus allocating an skb requires
> an O(3) memory allocation. Under heavy memory loads and fragmentation, such
> a request can fail. Previous versions of the driver have dropped the packet
> and reused the old buffer; however, the new version introduced a bug in that
> it released the old buffer before trying to allocate a new one. The previous
> method is implemented here.
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@vger.kernel.org> [v3.18]
> Reported-by: Eric Biggers <ebiggers3@gmail.com>
> Cc: Eric Biggers <ebiggers3@gmail.com>
> ---
>
> V2 - Fixes an error in the logic of V1. Realtek is working on a change to
> the RX buffer allocation, but that is likely to be too invasive for
> a fix to -rc or stable. In the meantime, this will help.
23/23? Where are patches 1-22? I don't see them in patchwork:
https://patchwork.kernel.org/project/linux-wireless/list/
--
Kalle Valo
next prev parent reply other threads:[~2014-12-28 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 20:17 [PATCH 23/23 V2 for 3.19] rtlwifi: Fix error when accessing unmapped memory in skb Larry Finger
2014-12-28 5:50 ` Kalle Valo [this message]
2014-12-28 6:15 ` Larry Finger
2014-12-28 6:15 ` Larry Finger
2015-01-05 9:20 ` Kalle Valo
2015-01-05 21:25 ` Larry Finger
2015-01-06 8:10 ` Kalle Valo
2014-12-31 0:49 ` Eric Biggers
2014-12-31 3:31 ` Larry Finger
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=87a928726w.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=ebiggers3@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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.