From: kernel test robot <lkp@intel.com> To: Stefan Roesch <shr@fb.com>, io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org Cc: kbuild-all@lists.01.org, shr@fb.com Subject: Re: [PATCH v1 1/5] fs: make user_path_at_empty() take a struct filename Date: Tue, 30 Nov 2021 10:09:03 +0800 [thread overview] Message-ID: <202111301052.fMLJlgVf-lkp@intel.com> (raw) In-Reply-To: <20211129221257.2536146-2-shr@fb.com> Hi Stefan, Thank you for the patch! Yet something to improve: [auto build test ERROR on c2626d30f312afc341158e07bf088f5a23b4eeeb] url: https://github.com/0day-ci/linux/commits/Stefan-Roesch/io_uring-add-xattr-support/20211130-061448 base: c2626d30f312afc341158e07bf088f5a23b4eeeb config: m68k-defconfig (https://download.01.org/0day-ci/archive/20211130/202111301052.fMLJlgVf-lkp@intel.com/config) compiler: m68k-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/01c97d7409d5384e3cb760a9a99fa0c61899fc18 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Stefan-Roesch/io_uring-add-xattr-support/20211130-061448 git checkout 01c97d7409d5384e3cb760a9a99fa0c61899fc18 # save the config file to linux build tree mkdir build_dir COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All errors (new ones prefixed by >>, old ones prefixed by <<): >> ERROR: modpost: "getname_flags" [fs/ocfs2/ocfs2.ko] undefined! ERROR: modpost: "getname_flags" [fs/xfs/xfs.ko] undefined! >> ERROR: modpost: "getname_flags" [fs/coda/coda.ko] undefined! --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v1 1/5] fs: make user_path_at_empty() take a struct filename Date: Tue, 30 Nov 2021 10:09:03 +0800 [thread overview] Message-ID: <202111301052.fMLJlgVf-lkp@intel.com> (raw) In-Reply-To: <20211129221257.2536146-2-shr@fb.com> [-- Attachment #1: Type: text/plain, Size: 1634 bytes --] Hi Stefan, Thank you for the patch! Yet something to improve: [auto build test ERROR on c2626d30f312afc341158e07bf088f5a23b4eeeb] url: https://github.com/0day-ci/linux/commits/Stefan-Roesch/io_uring-add-xattr-support/20211130-061448 base: c2626d30f312afc341158e07bf088f5a23b4eeeb config: m68k-defconfig (https://download.01.org/0day-ci/archive/20211130/202111301052.fMLJlgVf-lkp(a)intel.com/config) compiler: m68k-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/01c97d7409d5384e3cb760a9a99fa0c61899fc18 git remote add linux-review https://github.com/0day-ci/linux git fetch --no-tags linux-review Stefan-Roesch/io_uring-add-xattr-support/20211130-061448 git checkout 01c97d7409d5384e3cb760a9a99fa0c61899fc18 # save the config file to linux build tree mkdir build_dir COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp@intel.com> All errors (new ones prefixed by >>, old ones prefixed by <<): >> ERROR: modpost: "getname_flags" [fs/ocfs2/ocfs2.ko] undefined! ERROR: modpost: "getname_flags" [fs/xfs/xfs.ko] undefined! >> ERROR: modpost: "getname_flags" [fs/coda/coda.ko] undefined! --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next prev parent reply other threads:[~2021-11-30 2:09 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-29 22:12 [PATCH v1 0/5] io_uring: add xattr support Stefan Roesch 2021-11-29 22:12 ` [PATCH v1 1/5] fs: make user_path_at_empty() take a struct filename Stefan Roesch 2021-11-30 2:09 ` kernel test robot [this message] 2021-11-30 2:09 ` kernel test robot 2021-11-29 22:12 ` [PATCH v1 2/5] fs: split off setxattr_setup function from setxattr Stefan Roesch 2021-11-29 22:12 ` [PATCH v1 3/5] fs: split off the vfs_getxattr from getxattr Stefan Roesch 2021-11-30 13:40 ` [fs] 23a831cdec: WARNING:at_include/linux/thread_info.h:#do_getxattr kernel test robot 2021-11-30 13:40 ` kernel test robot 2021-11-29 22:12 ` [PATCH v1 4/5] io_uring: add fsetxattr and setxattr support Stefan Roesch 2021-11-29 22:12 ` [PATCH v1 5/5] io_uring: add fgetxattr and getxattr support Stefan Roesch 2021-11-30 1:08 ` [PATCH v1 0/5] io_uring: add xattr support Clay Harris 2021-11-30 3:16 ` Andreas Dilger 2021-11-30 6:37 ` Clay Harris 2021-11-30 6:53 ` Clay Harris 2021-11-30 11:40 ` Clay Harris 2021-11-30 7:19 ` Dave Chinner 2021-12-01 6:16 ` Stefan Roesch 2021-12-01 6:07 ` Stefan Roesch 2021-12-01 7:46 ` Clay Harris 2021-12-01 13:14 ` Christian Brauner 2021-12-01 12:19 ` Stefan Metzmacher 2021-12-01 19:52 ` Clay Harris 2021-12-01 20:05 ` Andreas Dilger 2021-12-03 17:58 ` Stefan Roesch
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=202111301052.fMLJlgVf-lkp@intel.com \ --to=lkp@intel.com \ --cc=io-uring@vger.kernel.org \ --cc=kbuild-all@lists.01.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=shr@fb.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: linkBe 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.