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
Larry Finger <[email protected]> writes:
> 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.
So this is the patch:
https://patchwork.kernel.org/patch/10687671/
> I just checked, and this one-line patch is still sitting in patchwork
> with a status of "NEW". Why is this the case?
I just have been busy with other stuff and haven't had enough free time
to process patches.
> 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+!
Sure, I understand that. I'll try to apply the patch soon.
--
Kalle Valo