From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry.memverge@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 3/3] mm/migrate: Create move_phys_pages syscall
Date: Sat, 9 Sep 2023 06:43:54 +0800 [thread overview]
Message-ID: <202309090612.A9EmQIQ1-lkp@intel.com> (raw)
In-Reply-To: <20230907075453.350554-4-gregory.price@memverge.com>
Hi Gregory,
[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 tip/x86/asm linus/master next-20230908]
[cannot apply to arnd-asm-generic/master v6.5]
[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/Gregory-Price/mm-migrate-remove-unused-mm-argument-from-do_move_pages_to_node/20230909-004600
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20230907075453.350554-4-gregory.price%40memverge.com
patch subject: [RFC PATCH 3/3] mm/migrate: Create move_phys_pages syscall
config: x86_64-buildonly-randconfig-002-20230909 (https://download.01.org/0day-ci/archive/20230909/202309090612.A9EmQIQ1-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230909/202309090612.A9EmQIQ1-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/202309090612.A9EmQIQ1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/migrate.c:2182:42: error: no member named 'owner' in 'struct mm_struct'
struct task_struct *owner = vma->vm_mm->owner;
~~~~~~~~~~ ^
1 error generated.
vim +2182 mm/migrate.c
2170
2171 /*
2172 * Walks each vma mapping a given page and determines if those
2173 * vma's are both migratable, and that the target node is within
2174 * the allowed cpuset of the owning task.
2175 */
2176 static bool phys_page_migratable(struct folio *folio,
2177 struct vm_area_struct *vma,
2178 unsigned long address,
2179 void *arg)
2180 {
2181 struct rmap_page_ctxt *ctxt = (struct rmap_page_ctxt *)arg;
> 2182 struct task_struct *owner = vma->vm_mm->owner;
2183 nodemask_t task_nodes = cpuset_mems_allowed(owner);
2184
2185 ctxt->found |= true;
2186 ctxt->migratable &= vma_migratable(vma);
2187 ctxt->node_allowed &= node_isset(ctxt->node, task_nodes);
2188
2189 return ctxt->migratable && ctxt->node_allowed;
2190 }
2191
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-08 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230907075453.350554-4-gregory.price@memverge.com>
2023-09-08 22:33 ` [RFC PATCH 3/3] mm/migrate: Create move_phys_pages syscall kernel test robot
2023-09-08 22:43 ` 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=202309090612.A9EmQIQ1-lkp@intel.com \
--to=lkp@intel.com \
--cc=gourry.memverge@gmail.com \
--cc=llvm@lists.linux.dev \
--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