Hi,
I used 4.18.11 for a while and noticed a memleak showing
in slabtop as kmalloc-2048. Then I updated to 4.18.16
and enabled kmemleak, it dumps this:
unreferenced object 0xa10a5cc49800 (size 2048):
comm "conky", pid 2734, jiffies 4295635396 (age 454.650s)
hex dump (first 32 bytes):
On Mon, 2018-10-22 at 10:02 +0200, Johannes Stezenbach wrote:
>
> [] sta_set_sinfo+0x634/0x900 [mac80211]
> [] ieee80211_get_station+0x50/0x70 [mac80211]
> [<9fd8a7aa>] cfg80211_wext_giwrate+0x111/0x2b0 [cfg80211]
> I guess it relates to
> 0
On Mon, Oct 22, 2018 at 10:25:07AM +0200, Johannes Berg wrote:
> On Mon, 2018-10-22 at 10:02 +0200, Johannes Stezenbach wrote:
> >
> > [] sta_set_sinfo+0x634/0x900 [mac80211]
> > [] ieee80211_get_station+0x50/0x70 [mac80211]
> > [<9fd8a7aa>]
On Mon, 2018-10-22 at 10:35 +0200, Johannes Stezenbach wrote:
> > commit 848e616e66d4592fe9afc40743d3504deb7632b4
> > Author: Stefan Seyfried
> > Date: Sun Sep 30 12:53:00 2018 +0200
> >
> > cfg80211: fix wext-compat memory leak
> >
> > Hopefully that'll eventually propagate to stable.
>
On 10/22/2018 10:37 AM, Johannes Berg wrote:
On Mon, 2018-10-22 at 10:35 +0200, Johannes Stezenbach wrote:
commit 848e616e66d4592fe9afc40743d3504deb7632b4
Author: Stefan Seyfried
Date: Sun Sep 30 12:53:00 2018 +0200
cfg80211: fix wext-compat memory leak
Hopefully that'll eventually pro
Arend van Spriel writes:
> On 10/22/2018 10:37 AM, Johannes Berg wrote:
>> On Mon, 2018-10-22 at 10:35 +0200, Johannes Stezenbach wrote:
>>
commit 848e616e66d4592fe9afc40743d3504deb7632b4
Author: Stefan Seyfried
Date: Sun Sep 30 12:53:00 2018 +0200
cfg80211: fix we
