Greg,
Is the fix for a memory leak in the wext compat layer queued for stable? It is
in kernel:HEAD as commit 848e616e66d4592fe9afc40743d3504deb7632b4 ("cfg80211:
fix wext-compat memory leak")
I just receiv3ed a complaint about a leak for a system that is running Ubuntu's
kernel 4.19.
Unfortunately, this commit has a "fixes" line, but not a Cc for Stable.
Larry
On Wed, Oct 31, 2018 at 01:49:21PM -0500, Larry Finger wrote:
> Greg,
>
> Is the fix for a memory leak in the wext compat layer queued for stable? It
> is in kernel:HEAD as commit 848e616e66d4592fe9afc40743d3504deb7632b4
> ("cfg80211: fix wext-compat memory leak")
>
> I just receiv3ed a complaint about a leak for a system that is running
> Ubuntu's kernel 4.19.
That would be very odd as commit
848e616e66d4592fe9afc40743d3504deb7632b4 is in 4.19, it was in 4.19-rc7.
> Unfortunately, this commit has a "fixes" line, but not a Cc for Stable.
It could have gone into the 4.18-stable tree, but that is now
end-of-life, sorry.
greg k-h
On 11/29/18 6:50 AM, Greg Kroah-Hartman wrote:
> On Wed, Oct 31, 2018 at 01:49:21PM -0500, Larry Finger wrote:
>> Greg,
>>
>> Is the fix for a memory leak in the wext compat layer queued for stable? It
>> is in kernel:HEAD as commit 848e616e66d4592fe9afc40743d3504deb7632b4
>> ("cfg80211: fix wext-compat memory leak")
>>
>> I just receiv3ed a complaint about a leak for a system that is running
>> Ubuntu's kernel 4.19.
>
> That would be very odd as commit
> 848e616e66d4592fe9afc40743d3504deb7632b4 is in 4.19, it was in 4.19-rc7.
>
>> Unfortunately, this commit has a "fixes" line, but not a Cc for Stable.
>
> It could have gone into the 4.18-stable tree, but that is now
> end-of-life, sorry.
Too bad, but thanks for the reply.
Larry