[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2204051224560.47162@angie.orcam.me.uk>
Date: Tue, 5 Apr 2022 12:31:58 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
cc: Andrew Powers-Holmes <aholmes@...om.net>,
yaliang.wang@...driver.com, rppt@...nel.org, huangpei@...ngson.cn,
Andrew Morton <akpm@...ux-foundation.org>, kumba@...too.org,
Geert Uytterhoeven <geert@...ux-m68k.org>,
anshuman.khandual@....com, penberg@...nel.org,
linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] MIPS: pgalloc: fix memory leak caused by pgd_free()
On Tue, 5 Apr 2022, Thomas Bogendoerfer wrote:
> > 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.
Hmm, not all fixes qualify for or indeed are worth backporting and I'd
expect those that have no stable annotation to remain on trunk only. I
have been following this principle with my submissions anyway.
Indeed I can see a backport to 5.17 has literally just been posted in
this humongous patch set, but in this case I suspect Greg has just picked
this up by hand (thanks, Greg!) having seen this discussion (though how he
manages to escape alive through the flood of messages has been astonishing
me).
Maciej
Powered by blists - more mailing lists