From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Johannes Stezenbach <js@sig21.net>,
Arend van Spriel <aspriel@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: 4.18.16: memory leak in sta_set_sinfo
Date: Tue, 23 Oct 2018 14:59:51 +0300 [thread overview]
Message-ID: <87bm7kdgaw.fsf@purkki.adurom.net> (raw)
In-Reply-To: <2ad39f6f-c01a-f51c-e114-641d11a5eb22@broadcom.com> (Arend van Spriel's message of "Mon, 22 Oct 2018 12:48:31 +0200")
Arend van Spriel <arend.vanspriel@broadcom.com> 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 <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.
>>
>> Well, normally it works automatically when you have a Fixes tag, so I
>> don't usually try to queue anything manually. Maybe Greg has had his
>> hands full with the 4.19 release :-)
>
> Missed the memo. Does that mean Cc: to stable is no longer needed? It
> is still documented as such in
> Documentation/process/stable-kernel-rules.rst.
I haven't seen any memos either but in lot of cases having just Fixes
line seems to be enough to get the patch to stable releases. If someone
has any documentation about this, please do share.
--
Kalle Valo
prev parent reply other threads:[~2018-10-23 11:59 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
2018-10-22 8:37 ` Johannes Berg
2018-10-22 10:48 ` Arend van Spriel
2018-10-23 11:59 ` Kalle Valo [this message]
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=87bm7kdgaw.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=aspriel@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=js@sig21.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