All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Roman Kagan <rkagan@amazon.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC 2/3] mm/secretmem: implement mm-local kernel allocations
Date: Thu, 27 Jun 2024 06:43:15 +0800	[thread overview]
Message-ID: <202406270637.kuvejkNW-lkp@intel.com> (raw)
In-Reply-To: <20240621201501.1059948-3-rkagan@amazon.de>

Hi Roman,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on akpm-mm/mm-everything]
[also build test ERROR on char-misc/char-misc-testing char-misc/char-misc-next char-misc/char-misc-linus shuah-kselftest/next shuah-kselftest/fixes linus/master v6.10-rc5 next-20240626]
[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/Roman-Kagan/mseal-expose-interface-to-seal-unseal-user-memory-ranges/20240625-174709
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20240621201501.1059948-3-rkagan%40amazon.de
patch subject: [PATCH RFC 2/3] mm/secretmem: implement mm-local kernel allocations
config: parisc-allnoconfig (https://download.01.org/0day-ci/archive/20240627/202406270637.kuvejkNW-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240627/202406270637.kuvejkNW-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/202406270637.kuvejkNW-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/gup.c: In function 'follow_page':
>> mm/gup.c:1175:14: error: implicit declaration of function 'can_access_secretmem_vma' [-Werror=implicit-function-declaration]
    1175 |         if (!can_access_secretmem_vma(vma))
         |              ^~~~~~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors


vim +/can_access_secretmem_vma +1175 mm/gup.c

  1168	
  1169	struct page *follow_page(struct vm_area_struct *vma, unsigned long address,
  1170				 unsigned int foll_flags)
  1171	{
  1172		struct follow_page_context ctx = { NULL };
  1173		struct page *page;
  1174	
> 1175		if (!can_access_secretmem_vma(vma))
  1176			return NULL;
  1177	
  1178		if (WARN_ON_ONCE(foll_flags & FOLL_PIN))
  1179			return NULL;
  1180	
  1181		/*
  1182		 * We never set FOLL_HONOR_NUMA_FAULT because callers don't expect
  1183		 * to fail on PROT_NONE-mapped pages.
  1184		 */
  1185		page = follow_page_mask(vma, address, foll_flags, &ctx);
  1186		if (ctx.pgmap)
  1187			put_dev_pagemap(ctx.pgmap);
  1188		return page;
  1189	}
  1190	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-06-26 22:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 20:14 [PATCH RFC 0/3] add support for mm-local memory allocations Roman Kagan
2024-06-21 20:14 ` [PATCH RFC 1/3] mseal: expose interface to seal / unseal user memory ranges Roman Kagan
2024-06-21 20:15 ` [PATCH RFC 2/3] mm/secretmem: implement mm-local kernel allocations Roman Kagan
2024-06-26 22:43   ` kernel test robot [this message]
2024-06-26 23:06   ` kernel test robot
2024-06-21 20:15 ` [PATCH RFC 3/3] drivers/misc: add test driver and selftest for proclocal allocator Roman Kagan
2024-07-03 14:36   ` Greg Kroah-Hartman
2024-07-04 11:11 ` [PATCH RFC 0/3] add support for mm-local memory allocations David Woodhouse
2024-08-28  9:50 ` Alexander Graf
  -- strict thread matches above, loose matches on Subject: below --
2024-06-29  9:09 [PATCH RFC 2/3] mm/secretmem: implement mm-local kernel allocations kernel test robot

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=202406270637.kuvejkNW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rkagan@amazon.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.