Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Arend van Spriel <aspriel@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: 4.18.16: memory leak in sta_set_sinfo
Date: Mon, 22 Oct 2018 10:35:52 +0200	[thread overview]
Message-ID: <20181022083552.GA6878@sig21.net> (raw)
In-Reply-To: <f1f5e0839f4b1b68510b9db398995c859a19a19e.camel@sipsolutions.net>

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:
> > 
> >     [<00000000b7b13d1a>] sta_set_sinfo+0x634/0x900 [mac80211]
> >     [<00000000a74db622>] ieee80211_get_station+0x50/0x70 [mac80211]
> >     [<000000009fd8a7aa>] cfg80211_wext_giwrate+0x111/0x2b0 [cfg80211]
> 
> > I guess it relates to
> > 0fdf1493b41 " mac80211: allocate and fill tidstats only when needed"
> > which Fixes: 8689c051a201 ("cfg80211: dynamically allocate per-tid stats for station info")
> 
> Yes, you're using wext which we don't any more, so we didn't see this.

Yes, disappointing that conky still uses wext.

> However, it's already fixed:
> 
> commit 848e616e66d4592fe9afc40743d3504deb7632b4
> Author: Stefan Seyfried <seife+kernel@b1-systems.com>
> Date:   Sun Sep 30 12:53:00 2018 +0200
> 
>     cfg80211: fix wext-compat memory leak
> 
> Hopefully that'll eventually propagate to stable.

Good to know it's fixed, but "hopefully" makes me wonder,
I'd love to hear the confirmation that it's been queued.
OTOH I'll apply the patch locally and eventually move to 4.19,
so what gives...

Thanks,
Johannes

  reply	other threads:[~2018-10-22  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22  8:02 4.18.16: memory leak in sta_set_sinfo Johannes Stezenbach
2018-10-22  8:25 ` Johannes Berg
2018-10-22  8:35   ` Johannes Stezenbach [this message]
2018-10-22  8:37     ` Johannes Berg
2018-10-22 10:48       ` Arend van Spriel
2018-10-23 11:59         ` 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=20181022083552.GA6878@sig21.net \
    --to=js@sig21.net \
    --cc=aspriel@gmail.com \
    --cc=johannes@sipsolutions.net \
    --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