linux-kernel - Re: [PATCH] selftest: mm: Test if hugepage does not get leaked during __bio_release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20240523195734.bc03a8822a34b1a97880fb65@linux-foundation.org>
Date: Thu, 23 May 2024 19:57:34 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Hildenbrand <david@...hat.com>
Cc: Donet Tom <donettom@...ux.ibm.com>, Shuah Khan <shuah@...nel.org>,
 Matthew Wilcox <willy@...radead.org>, Tony Battersby
 <tonyb@...ernetics.com>, linux-mm@...ck.org,
 linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org, Ritesh
 Harjani <ritesh.list@...il.com>, Mike Rapoport <rppt@...nel.org>, Muchun
 Song <songmuchun@...edance.com>, stable@...r.kernel.org
Subject: Re: [PATCH] selftest: mm: Test if hugepage does not get leaked
 during __bio_release_pages()

On Thu, 23 May 2024 22:40:25 +0200 David Hildenbrand <david@...hat.com> wrote:

> > You have stable@...r.kernel.org in the mail headers, so I assume you're
> > proposing this for backporting.  When doing this, please include
> > 
> > Cc: <stable@...r.kernel.org>
> > 
> > in the changelog footers and also include a Fixes: target.  I'm
> > assuming the suitable Fixes: target for this patch is 38b43539d64b?
> 
> This adds a new selfest to make sure what was fixed (and backported to 
> stable) remains fixed.

Sure.  But we should provide -stable maintainers guidance for "how far
back to go".  There isn't much point in backporting this into kernels
where it's known to fail!

I'm still thinking that we want this in kernels which have 38b43539d64b?