From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Andrew Powers-Holmes <aholmes@omnom.net>,
yaliang.wang@windriver.com, rppt@kernel.org,
huangpei@loongson.cn, Andrew Morton <akpm@linux-foundation.org>,
kumba@gentoo.org, Geert Uytterhoeven <geert@linux-m68k.org>,
anshuman.khandual@arm.com, penberg@kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] MIPS: pgalloc: fix memory leak caused by pgd_free()
Date: Tue, 5 Apr 2022 12:45:06 +0200 [thread overview]
Message-ID: <20220405104506.GA17085@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2204051027490.47162@angie.orcam.me.uk>
On Tue, Apr 05, 2022 at 10:42:21AM +0100, Maciej W. Rozycki wrote:
> On Mon, 4 Apr 2022, Andrew Powers-Holmes wrote:
>
> > Would the best way to get this merged into 5.10/15 (and maybe .16 just
> > for good measure) be to email the stable team (since it's already in
> > Linus' tree)? Documentation/process/stable-kernel-rules seems to say
> > yes, but I'd like to avoid stepping on anyone's toes given that it's not
> > my patch.
>
> You seem the most severely affected so far, so why not act in your best
> interest? I think option #2 applies here and seems quite straightforward
> to follow, referring commit 2bc5bab9a763 and using your use case as the
> justification. It doesn't have to be the author to request a backport.
>
> NB I think it has to be backported to all the stable branches made since
> the original breakage; i.e. v5.9+ (I haven't kept track of what they are).
the fix has a Fixes tag so it will usually ported to stable/longterm kernels.
I already saw it in Greg's patch bombs.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-04-06 0:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:31 yaliang.wang
2022-03-14 14:51 ` Thomas Bogendoerfer
2022-04-02 13:48 ` Maciej W. Rozycki
2022-04-03 3:34 ` Andrew Holmes
2022-04-03 10:37 ` Maciej W. Rozycki
2022-04-04 13:16 ` Andrew Powers-Holmes
2022-04-05 9:42 ` Maciej W. Rozycki
2022-04-05 10:45 ` Thomas Bogendoerfer [this message]
2022-04-05 11:31 ` Maciej W. Rozycki
2022-04-04 21:10 ` Joshua Kinard
2022-04-03 4:15 ` Donald Hoskins
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=20220405104506.GA17085@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=aholmes@omnom.net \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=huangpei@loongson.cn \
--cc=kumba@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=penberg@kernel.org \
--cc=rppt@kernel.org \
--cc=yaliang.wang@windriver.com \
/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
all inboxes | Powered by JetHome®