From: kernel test robot <lkp@intel.com>
To: Abhishek Bapat <abhishekbapat@google.com>,
Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Hao Ge <hao.ge@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Sourav Panda <souravpanda@google.com>,
Abhishek Bapat <abhishekbapat@google.com>
Subject: Re: [PATCH v4 6/6] kselftest: alloc_tag: extend the allocinfo ioctl kselftest
Date: Thu, 11 Jun 2026 03:42:24 +0800 [thread overview]
Message-ID: <202606110300.R4LPBVBO-lkp@intel.com> (raw)
In-Reply-To: <d0a8308b4d0799876d24461a8ed9b5a71d3e1e89.1781042698.git.abhishekbapat@google.com>
Hi Suren,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on next-20260609]
[cannot apply to akpm-mm/mm-nonmm-unstable shuah-kselftest/next shuah-kselftest/fixes linus/master v7.1-rc7]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Abhishek-Bapat/alloc_tag-add-ioctl-to-proc-allocinfo/20260610-081508
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/d0a8308b4d0799876d24461a8ed9b5a71d3e1e89.1781042698.git.abhishekbapat%40google.com
patch subject: [PATCH v4 6/6] kselftest: alloc_tag: extend the allocinfo ioctl kselftest
config: sparc64-randconfig-r061-20260610 (https://download.01.org/0day-ci/archive/20260611/202606110300.R4LPBVBO-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260611/202606110300.R4LPBVBO-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/202606110300.R4LPBVBO-lkp@intel.com/
All errors (new ones prefixed by >>):
lib/alloc_tag.c: In function 'allocinfo_compat_ioctl':
>> lib/alloc_tag.c:346:58: error: implicit declaration of function 'compat_ptr' [-Wimplicit-function-declaration]
346 | return allocinfo_ioctl(file, cmd, (unsigned long)compat_ptr(arg));
| ^~~~~~~~~~
vim +/compat_ptr +346 lib/alloc_tag.c
341
342 #ifdef CONFIG_COMPAT
343 static long allocinfo_compat_ioctl(struct file *file, unsigned int cmd,
344 unsigned long arg)
345 {
> 346 return allocinfo_ioctl(file, cmd, (unsigned long)compat_ptr(arg));
347 }
348 #endif
349
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-06-10 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 0:12 [PATCH v4 0/6] alloc_tag: introduce IOCTL-based filtering for MAP Abhishek Bapat
2026-06-10 0:12 ` [PATCH v4 1/6] alloc_tag: add ioctl to /proc/allocinfo Abhishek Bapat
2026-06-10 1:28 ` Hao Ge
2026-06-10 11:23 ` Usama Arif
2026-06-10 0:12 ` [PATCH v4 2/6] alloc_tag: add ioctl filters " Abhishek Bapat
2026-06-10 1:45 ` Hao Ge
2026-06-10 0:12 ` [PATCH v4 3/6] alloc_tag: add size-based filtering to ioctl Abhishek Bapat
2026-06-10 1:49 ` Hao Ge
2026-06-10 0:12 ` [PATCH v4 4/6] alloc_tag: add accuracy based " Abhishek Bapat
2026-06-10 1:52 ` Hao Ge
2026-06-10 0:12 ` [PATCH v4 5/6] kselftest: alloc_tag: add kselftest for ioctl interface Abhishek Bapat
2026-06-10 3:17 ` Hao Ge
2026-06-10 0:12 ` [PATCH v4 6/6] kselftest: alloc_tag: extend the allocinfo ioctl kselftest Abhishek Bapat
2026-06-10 9:33 ` Hao Ge
2026-06-10 19:42 ` kernel test robot [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=202606110300.R4LPBVBO-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhishekbapat@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=hao.ge@linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=souravpanda@google.com \
--cc=surenb@google.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