From: Andrew Morton <akpm@linux-foundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Lorenzo Stoakes via B4 Relay
<devnull+lorenzo.stoakes.oracle.com@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/testing/vma: add missing function stub
Date: Thu, 29 May 2025 08:23:59 -0700 [thread overview]
Message-ID: <20250529082359.ebf2a908e068ed3ffc8027f9@linux-foundation.org> (raw)
In-Reply-To: <8bcf5f5a-a4e6-41cb-84a8-e2919b0785cb@lucifer.local>
On Thu, 29 May 2025 06:39:09 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
> On Wed, May 28, 2025 at 03:52:18PM -0700, Andrew Morton wrote:
> > On Wed, 28 May 2025 15:15:39 +0100 Lorenzo Stoakes via B4 Relay <devnull+lorenzo.stoakes.oracle.com@kernel.org> wrote:
> >
> > > From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > >
> > > The hugetlb fix introduced in commit ee40c9920ac2 ("mm: fix copy_vma()
> > > error handling for hugetlb mappings") mistakenly did not provide a stub for
> > > the VMA userland testing, which results in a compile error when trying to
> > > build this.
> >
> > Thanks, I'll add the Fixes: and the cc:stable (because ee40c9920ac2 had
> > cc:stable).
>
> Yeah I intentionally excluded those, as it'll lead to some backport pain
> for something that isn't shipped.
>
> I'm not sure if we generally backport test fixes as a rule? Though I
> suppose it might be useful if somebody is investigating an issue in a
> stable kernel.
I do like to backport selftests fixes if doing so avoids bogus failures
and especially if they fix build breakage.
next prev parent reply other threads:[~2025-05-29 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 14:15 Lorenzo Stoakes via B4 Relay
2025-05-28 14:40 ` Liam R. Howlett
2025-05-28 22:52 ` Andrew Morton
2025-05-29 5:39 ` Lorenzo Stoakes
2025-05-29 15:23 ` Andrew Morton [this message]
2025-05-29 8:39 ` Pedro Falcato
2025-05-30 5:15 ` Oliver Sang
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=20250529082359.ebf2a908e068ed3ffc8027f9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=devnull+lorenzo.stoakes.oracle.com@kernel.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=vbabka@suse.cz \
/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