From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Barry Song <baohua@kernel.org>,
David Hildenbrand <david@kernel.org>, Dev Jain <dev.jain@arm.com>,
Jason Gunthorpe <jgg@nvidia.com>,
Liam Howlett <liam.howlett@oracle.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>, Zi Yan <ziy@nvidia.com>,
Damien Le Moal <dlemoal@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-mm@kvack.org
Subject: Re: [linux-next:master] [tools/testing/vma] 28d7ff9930: ktools.vma.make.fail
Date: Tue, 27 Jan 2026 10:17:44 +0000 [thread overview]
Message-ID: <36add8cf-86dd-4dc2-a538-a4b413f54e96@lucifer.local> (raw)
In-Reply-To: <a87f818d-7912-4d2d-9f96-11a57ada296c@lucifer.local>
On Tue, Jan 27, 2026 at 10:05:57AM +0000, Lorenzo Stoakes wrote:
> On Tue, Jan 27, 2026 at 08:18:12AM +0000, Lorenzo Stoakes wrote:
> > On Tue, Jan 27, 2026 at 02:13:11PM +0800, kernel test robot wrote:
> > >
> > >
> > > Hello,
> > >
> > > kernel test robot noticed "ktools.vma.make.fail" on:
> >
> > Thanks to whoever set this up :) so far VMA userland tests have not been
> > exercised very much and I've had to find issues manually :)
> >
> > >
> > > commit: 28d7ff99300f3a897eb6419efafdbcf96978f637 ("tools/testing/vma: separate out vma_internal.h into logical headers")
> > > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> >
> > Hm this is strange, this works perfectly fine locally at this commit.
> >
> > But it does seem this is duplicated so will fix-patch at this point in the series.
>
> Fixed at https://lore.kernel.org/linux-mm/1e032732-61c3-485c-9aa7-6a09016fefc1@lucifer.local/
>
> >
> > I notice the build is broken however at tip on next (will bisect), I guess the
> > bot hasn't got there yet? Seems somebody added a compiler directive that is not
> > stubbed out yet.
> >
> > I might simply fix by adding to this commit as a stub to avoid hassle with
> > chasing down the offending patch...
>
> OK so the other thing needs a fix in a tools header, so will report separately.
>
> Cheers, Lorenzo
Reported at https://lore.kernel.org/all/0c2d9b69-c052-4075-8a4b-023d277b8509@lucifer.local/
prev parent reply other threads:[~2026-01-27 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 6:13 kernel test robot
2026-01-27 8:18 ` Lorenzo Stoakes
2026-01-27 10:05 ` Lorenzo Stoakes
2026-01-27 10:17 ` Lorenzo Stoakes [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=36add8cf-86dd-4dc2-a538-a4b413f54e96@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=djwong@kernel.org \
--cc=dlemoal@kernel.org \
--cc=jgg@nvidia.com \
--cc=liam.howlett@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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