From: Lance Yang <ioworker0@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 9312/9709] sh4-linux-ld: rmap.c:undefined reference to `split_huge_pmd_locked'
Date: Wed, 1 May 2024 17:15:46 +0800 [thread overview]
Message-ID: <CAK1f24mHUM+n2OnZR9YuTZihsZctZJpKK=L-9jMzBNwDjc=XXQ@mail.gmail.com> (raw)
In-Reply-To: <202405011728.yuc8zquM-lkp@intel.com>
Hi all,
This bug was also introduced in v3[1] and has been fixed in v4[2].
Sorry again for any trouble this may have caused :(
[1] https://lore.kernel.org/linux-mm/20240429132308.38794-1-ioworker0@gmail.com
[2] https://lore.kernel.org/linux-mm/20240501042700.83974-1-ioworker0@gmail.com
Thanks,
Lance Yang
On Wed, May 1, 2024 at 5:12 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: d04466706db5e241ee026f17b5f920e50dee26b5
> commit: 6ae76ae5b2e07d4eb6b3e4fc594856d6500ade54 [9312/9709] mm/vmscan: avoid split lazyfree THP during shrink_folio_list()
> config: sh-defconfig (https://download.01.org/0day-ci/archive/20240501/202405011728.yuc8zquM-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240501/202405011728.yuc8zquM-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202405011728.yuc8zquM-lkp@intel.com/
>
> Note: the linux-next/master HEAD d04466706db5e241ee026f17b5f920e50dee26b5 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> sh4-linux-ld: mm/rmap.o: in function `try_to_unmap_one':
> rmap.c:(.text+0x2468): undefined reference to `unmap_huge_pmd_locked'
> >> sh4-linux-ld: rmap.c:(.text+0x246c): undefined reference to `split_huge_pmd_locked'
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-05-01 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 9:11 kernel test robot
2024-05-01 9:15 ` Lance Yang [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='CAK1f24mHUM+n2OnZR9YuTZihsZctZJpKK=L-9jMzBNwDjc=XXQ@mail.gmail.com' \
--to=ioworker0@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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