From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Critical fix for rtlwifi
Date: Wed, 12 Dec 2018 11:55:36 -0600 [thread overview]
Message-ID: <e419ff31-d9fe-feed-9f40-4a7d4b82a44e@lwfinger.net> (raw)
Kalle,
On November 18th, I submitted a patch entitles "[PATCH 4.20] rtlwifi: Fix leak
of skb when processing C2H_BT_INFO" that fixes an skb memory leak.
I just checked, and this one-line patch is still sitting in patchwork with a
status of "NEW". Why is this the case? The reports and testing of the fix took
place in a GitHub issue thread, but that should not keep a critical fix from
being handled fairly quickly. Meanwhile users of unpatched kernels are having
their systems run out of memory! This problem is present in kernels 4.18+!
Larry
next reply other threads:[~2018-12-12 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 17:55 Larry Finger [this message]
2018-12-13 9:40 ` Critical fix for rtlwifi Kalle Valo
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=e419ff31-d9fe-feed-9f40-4a7d4b82a44e@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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).