From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
oe-kbuild-all@lists.linux.dev,
David Hildenbrand <david@kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Chris Down <chris@chrisdown.name>
Subject: Re: [akpm-mm:mm-unstable 199/330] vm_util.c:127:14: error: too few arguments to function 'pagemap_scan_supported'
Date: Fri, 27 Mar 2026 10:55:42 +0000 [thread overview]
Message-ID: <ea001104-8f08-4175-90cf-f667f703b5bf@lucifer.local> (raw)
In-Reply-To: <202603271115.uE9vpppi-lkp@intel.com>
On Fri, Mar 27, 2026 at 11:20:28AM +0100, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: 74dc4627271e6e367176b519565e901ed72d6e4c
> commit: 9652b82ca963243fb80e645319d473a7dc65ee79 [199/330] selftests-mm-add-uffdio_move-huge-zeropage-pmd-regression-test-fix
> config: s390-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260327/202603271115.uE9vpppi-lkp@intel.com/config)
> compiler: s390x-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260327/202603271115.uE9vpppi-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/202603271115.uE9vpppi-lkp@intel.com/
>
> Note: the akpm-mm/mm-unstable HEAD 74dc4627271e6e367176b519565e901ed72d6e4c builds fine.
> It only hurts bisectability.
>
> All errors (new ones prefixed by >>):
>
> vm_util.c: In function 'pagemap_is_huge_zero':
> >> vm_util.c:127:14: error: too few arguments to function 'pagemap_scan_supported'
> 127 | if (!pagemap_scan_supported(fd))
> | ^~~~~~~~~~~~~~~~~~~~~~
> vm_util.c:70:13: note: declared here
> 70 | static bool pagemap_scan_supported(int fd, char *start)
> | ^~~~~~~~~~~~~~~~~~~~~~
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
>
See https://lore.kernel.org/linux-mm/815b2fc9-cee7-4bfa-8036-4b93d1b47b4e@lucifer.local/
This is because of a broken fix-patch that stuck around after something else got yanked.
Cheers, Lorenzo
prev parent reply other threads:[~2026-03-27 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 10:20 kernel test robot
2026-03-27 10:55 ` Lorenzo Stoakes (Oracle) [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=ea001104-8f08-4175-90cf-f667f703b5bf@lucifer.local \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chris@chrisdown.name \
--cc=david@kernel.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