From: Oliver Sang <oliver.sang@intel.com>
To: Pedro Falcato <pfalcato@suse.de>
Cc: <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<philip.li@intel.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH] tools/testing/vma: add missing function stub
Date: Fri, 30 May 2025 13:15:32 +0800 [thread overview]
Message-ID: <aDk+9IlV+gHc5jRL@xsang-OptiPlex-9020> (raw)
In-Reply-To: <upfmiz7u2t4tzd6oogqm52mmgecepv7ecojgysmosgcu6ggov4@hgqlp3x27754>
hi, Pedro,
On Thu, May 29, 2025 at 09:39:11AM +0100, Pedro Falcato wrote:
> On Wed, May 28, 2025 at 03:15:39PM +0100, Lorenzo Stoakes via B4 Relay 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.
> >
> > Provide this stub to resolve the issue.
> >
> > ---
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>
> Reviewed-by: Pedro Falcato <pfalcato@suse.de>
>
> I wonder if we could get the test bots to also build and run the userspace tests?
> It would help finding this before getting merged, while also actively testing
> vmas, xarray, maple, etc.
enabling other test suites under tools/testing besides selftests is in our plan.
unfortunately, we are still seeking resource to do it now.
>
> +Cc Oliver
>
> --
> Pedro
prev parent reply other threads:[~2025-05-30 5:16 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
2025-05-29 8:39 ` Pedro Falcato
2025-05-30 5:15 ` Oliver Sang [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=aDk+9IlV+gHc5jRL@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.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=philip.li@intel.com \
--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