From: kernel test robot <lkp@intel.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 2/5] userfaultfd: introduce access-likely mode for copy/wp operations
Date: Mon, 20 Jun 2022 18:33:52 +0800 [thread overview]
Message-ID: <202206201856.LMF3y588-lkp@intel.com> (raw)
In-Reply-To: <20220619233449.181323-3-namit@vmware.com>
Hi Nadav,
[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on linus/master v5.19-rc2 next-20220617]
[cannot apply to shuah-kselftest/next]
[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/intel-lab-lkp/linux/commits/Nadav-Amit/userfaultfd-support-access-write-hints/20220620-150942
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
config: hexagon-buildonly-randconfig-r001-20220620 (https://download.01.org/0day-ci/archive/20220620/202206201856.LMF3y588-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project af6d2a0b6825e71965f3e2701a63c239fa0ad70f)
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/intel-lab-lkp/linux/commit/ad1b8120bf00d273f9c786fe63c5c1fbcd7ff43c
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nadav-Amit/userfaultfd-support-access-write-hints/20220620-150942
git checkout ad1b8120bf00d273f9c786fe63c5c1fbcd7ff43c
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/userfaultfd.c:700:23: warning: parameter 'uffd_flags' set but not used [-Wunused-but-set-parameter]
uffd_flags_t uffd_flags)
^
mm/userfaultfd.c:711:23: warning: parameter 'uffd_flags' set but not used [-Wunused-but-set-parameter]
uffd_flags_t uffd_flags)
^
2 warnings generated.
vim +/uffd_flags +700 mm/userfaultfd.c
c1a4de99fada21 Andrea Arcangeli 2015-09-04 697
c1a4de99fada21 Andrea Arcangeli 2015-09-04 698 ssize_t mfill_zeropage(struct mm_struct *dst_mm, unsigned long start,
0b36999093ff22 Nadav Amit 2022-06-19 699 unsigned long len, atomic_t *mmap_changing,
0b36999093ff22 Nadav Amit 2022-06-19 @700 uffd_flags_t uffd_flags)
c1a4de99fada21 Andrea Arcangeli 2015-09-04 701 {
ad1b8120bf00d2 Nadav Amit 2022-06-19 702 /* There is no cost for setting the access bit of a zeropage */
ad1b8120bf00d2 Nadav Amit 2022-06-19 703 uffd_flags |= UFFD_FLAGS_ACCESS_LIKELY;
ad1b8120bf00d2 Nadav Amit 2022-06-19 704
f619147104c8ea Axel Rasmussen 2021-05-04 705 return __mcopy_atomic(dst_mm, start, 0, len, MCOPY_ATOMIC_ZEROPAGE,
f619147104c8ea Axel Rasmussen 2021-05-04 706 mmap_changing, 0);
f619147104c8ea Axel Rasmussen 2021-05-04 707 }
f619147104c8ea Axel Rasmussen 2021-05-04 708
--
0-DAY CI Kernel Test Service
https://01.org/lkp
parent reply other threads:[~2022-06-20 10:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220619233449.181323-3-namit@vmware.com>]
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=202206201856.LMF3y588-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=nadav.amit@gmail.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