From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: kernel test robot <lkp@intel.com>, linux-mm@kvack.org
Cc: kbuild-all@lists.01.org, akpm@linux-foundation.org,
Ben Widawsky <ben.widawsky@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Feng Tang <feng.tang@intel.com>, Michal Hocko <mhocko@kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Mel Gorman <mgorman@suse.de>,
Mike Kravetz <mike.kravetz@oracle.com>
Subject: Re: [PATCH v3 3/3] mm/mempolicy: wire up syscall set_mempolicy_home_node
Date: Fri, 29 Oct 2021 10:03:33 +0530 [thread overview]
Message-ID: <d1f685f8-26dd-39db-8e3a-25522e143f6d@linux.ibm.com> (raw)
In-Reply-To: <202110291150.kKMI1jaP-lkp@intel.com>
On 10/29/21 08:41, kernel test robot wrote:
> Hi "Aneesh,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on linus/master v5.15-rc7]
> [cannot apply to hnaz-mm/master tip/x86/asm next-20211028]
> [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]
>
> url: https://github.com/0day-ci/linux/commits/Aneesh-Kumar-K-V/mm-add-new-syscall-set_mempolicy_home_node/20211028-165859
> base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> config: h8300-randconfig-r016-20211028 (attached as .config)
> compiler: h8300-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://github.com/0day-ci/linux/commit/03cd3cdc88672826372b7c63c563949463ce8bc5
> git remote add linux-review https://github.com/0day-ci/linux
> git fetch --no-tags linux-review Aneesh-Kumar-K-V/mm-add-new-syscall-set_mempolicy_home_node/20211028-165859
> git checkout 03cd3cdc88672826372b7c63c563949463ce8bc5
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=h8300
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> arch/h8300/kernel/syscalls.c:7:36: warning: initialized field overwritten [-Woverride-init]
> 7 | #define __SYSCALL(nr, call) [nr] = (call),
> | ^
> include/uapi/asm-generic/unistd.h:883:1: note: in expansion of macro '__SYSCALL'
> 883 | __SYSCALL(__NR_process_mrelease, sys_process_mrelease)
> | ^~~~~~~~~
> arch/h8300/kernel/syscalls.c:7:36: note: (near initialization for '_sys_call_table[448]')
> 7 | #define __SYSCALL(nr, call) [nr] = (call),
> | ^
> include/uapi/asm-generic/unistd.h:883:1: note: in expansion of macro '__SYSCALL'
> 883 | __SYSCALL(__NR_process_mrelease, sys_process_mrelease)
> | ^~~~~~~~~
>
>
> vim +7 arch/h8300/kernel/syscalls.c
>
> 4e0c20981ec16d Yoshinori Sato 2015-01-28 5
> 4e0c20981ec16d Yoshinori Sato 2015-01-28 6 #undef __SYSCALL
> 4e0c20981ec16d Yoshinori Sato 2015-01-28 @7 #define __SYSCALL(nr, call) [nr] = (call),
> 4e0c20981ec16d Yoshinori Sato 2015-01-28 8
>
>
Thank you for reporting the failure.
modified include/uapi/asm-generic/unistd.h
@@ -880,7 +880,7 @@ __SYSCALL(__NR_memfd_secret, sys_memfd_secret)
#define __NR_process_mrelease 448
__SYSCALL(__NR_process_mrelease, sys_process_mrelease)
#define __NR_set_mempolicy_home_node 449
-__SYSCALL(__NR_process_mrelease, sys_process_mrelease)
+__SYSCALL(__NR_set_mempolicy_home_node, sys_set_mempolicy_home_node)
I will add that to the v4 update.
-aneesh
next prev parent reply other threads:[~2021-10-29 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 8:56 [PATCH v3 0/3] mm: add new " Aneesh Kumar K.V
2021-10-28 8:56 ` [PATCH v3 1/3] mm/mempolicy: use policy_node helper with MPOL_PREFERRED_MANY Aneesh Kumar K.V
2021-10-28 8:57 ` [PATCH v3 2/3] mm/mempolicy: add set_mempolicy_home_node syscall Aneesh Kumar K.V
2021-10-28 8:57 ` [PATCH v3 3/3] mm/mempolicy: wire up syscall set_mempolicy_home_node Aneesh Kumar K.V
2021-10-29 3:11 ` kernel test robot
2021-10-29 4:33 ` Aneesh Kumar K.V [this message]
2021-10-31 3:20 ` 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=d1f685f8-26dd-39db-8e3a-25522e143f6d@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ben.widawsky@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=mike.kravetz@oracle.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