From: Alistair Popple <apopple@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kernel test robot <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [linux-next:master] BUILD REGRESSION 10207e3a840b47b5eae573486a88fb6e29884f77
Date: Thu, 10 Feb 2022 12:18:07 +1100 [thread overview]
Message-ID: <1891248.islg2OGNBf@nvdebian> (raw)
In-Reply-To: <20220209161542.b7b831432382b0bd749b3e1f@linux-foundation.org>
On Thursday, 10 February 2022 11:15:42 AM AEDT Andrew Morton wrote:
> On Thu, 10 Feb 2022 11:09:55 +1100 Alistair Popple <apopple@nvidia.com> wrote:
>
> > On Thursday, 10 February 2022 6:34:46 AM AEDT Andrew Morton wrote:
> > > On Thu, 10 Feb 2022 02:51:05 +0800 kernel test robot <lkp@intel.com> wrote:
> > >
> > > > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > > branch HEAD: 10207e3a840b47b5eae573486a88fb6e29884f77 Add linux-next specific files for 20220209
> > > >
> > > > Error/Warning reports:
> > > >
> > > > https://lore.kernel.org/linux-mm/202201251833.Hon4gcuF-lkp@intel.com
> > > > https://lore.kernel.org/linux-mm/202201290705.x0MS0OCH-lkp@intel.com
> > > > https://lore.kernel.org/llvm/202202092059.9gegO2oq-lkp@intel.com
> > > >
> > > > ...
> > > >
> > > > ld: gup.c:(.text+0x1eff): undefined reference to `migrate_vma_pages'
> > > > ld: gup.c:(.text+0x1f44): undefined reference to `migrate_vma_finalize'
> > >
> > > Presumably CONFIG_MIGRATION=y, CONFIG_DEVICE_PRIVATE=n, so these
> > > functions aren't built.
> > >
> > > Methinks Alistair's "mm/gup.c: migrate device coherent pages when
> > > pinning instead of failing" needs some repair, please.
> >
> > Yes, that's the cause. The fix[1] from SeongJae looks correct.
>
> Yup.
>
> > What's easier
> > for you - taking that fix or me posting a v3 of my series including that now?
> >
> > [1] - https://lore.kernel.org/linux-mm/20220209094158.21941-3-sj@kernel.org/
> >
>
> Grabbing the little fixup is much simpler and easier, thanks.
Thanks, and I just noticed Christoph's pgmap refcount cleanup should also fix
this problem so if that ends up going in first this fix up shouldn't be needed.
next prev parent reply other threads:[~2022-02-10 1:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 18:51 [linux-next:master] BUILD REGRESSION 10207e3a840b47b5eae573486a88fb6e29884f77 kernel test robot
2022-02-09 19:34 ` Andrew Morton
2022-02-10 0:09 ` Alistair Popple
2022-02-10 0:15 ` Andrew Morton
2022-02-10 1:18 ` Alistair Popple [this message]
2022-02-10 6:00 ` Christoph Hellwig
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=1891248.islg2OGNBf@nvdebian \
--to=apopple@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).