From: Suren Baghdasaryan <surenb@google.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 5469/6165] uffd-common.c:636:28: warning: unused variable 'uffdio_move'
Date: Fri, 8 Dec 2023 09:27:38 -0800 [thread overview]
Message-ID: <CAJuCfpF_FN07Pvn5BJn1vJMAeEPKRBdfT3kWXVD=WAfizto+UQ@mail.gmail.com> (raw)
In-Reply-To: <202312081716.LUUhSNS4-lkp@intel.com>
On Fri, Dec 8, 2023 at 2:00 AM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: bc63de6e6ba0b16652c5fb4b9c9916b9e7ca1f23
> commit: d02321ca0329457d5828a83b82b156e6337c4236 [5469/6165] selftests/mm: add UFFDIO_MOVE ioctl test
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231208/202312081716.LUUhSNS4-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/202312081716.LUUhSNS4-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
Huh. This is strange. I checked linux-next.git and looks like the
patch adding the test [1] is there but the one actually adding new
ioctl [2] is missing (at least I do not see the new definitions in
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/include/uapi/linux/userfaultfd.h).
Patches belong to the same series. I'll check what's going on later
today.
[1] https://lore.kernel.org/all/20231206103702.3873743-6-surenb@google.com/
[2] https://lore.kernel.org/all/20231206103702.3873743-3-surenb@google.com/
>
> uffd-common.c: In function 'move_page':
> uffd-common.c:636:28: error: storage size of 'uffdio_move' isn't known
> 636 | struct uffdio_move uffdio_move;
> | ^~~~~~~~~~~
> uffd-common.c:643:28: error: 'UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES' undeclared (first use in this function)
> 643 | uffdio_move.mode = UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> uffd-common.c:643:28: note: each undeclared identifier is reported only once for each function it appears in
> uffd-common.c:645:24: error: 'UFFDIO_MOVE' undeclared (first use in this function); did you mean 'UFFDIO_COPY'?
> 645 | if (ioctl(ufd, UFFDIO_MOVE, &uffdio_move)) {
> | ^~~~~~~~~~~
> | UFFDIO_COPY
> >> uffd-common.c:636:28: warning: unused variable 'uffdio_move' [-Wunused-variable]
> 636 | struct uffdio_move uffdio_move;
> | ^~~~~~~~~~~
> --
> uffd-unit-tests.c:1323:42: error: 'UFFD_FEATURE_MOVE' undeclared here (not in a function); did you mean 'UFFD_EVENT_REMOVE'?
> 1323 | .uffd_feature_required = UFFD_FEATURE_MOVE,
> | ^~~~~~~~~~~~~~~~~
> | UFFD_EVENT_REMOVE
> uffd-common.c: In function 'move_page':
> uffd-common.c:636:28: error: storage size of 'uffdio_move' isn't known
> 636 | struct uffdio_move uffdio_move;
> | ^~~~~~~~~~~
> uffd-common.c:643:28: error: 'UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES' undeclared (first use in this function)
> 643 | uffdio_move.mode = UFFDIO_MOVE_MODE_ALLOW_SRC_HOLES;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> uffd-common.c:643:28: note: each undeclared identifier is reported only once for each function it appears in
> uffd-common.c:645:24: error: 'UFFDIO_MOVE' undeclared (first use in this function); did you mean 'UFFDIO_COPY'?
> 645 | if (ioctl(ufd, UFFDIO_MOVE, &uffdio_move)) {
> | ^~~~~~~~~~~
> | UFFDIO_COPY
> >> uffd-common.c:636:28: warning: unused variable 'uffdio_move' [-Wunused-variable]
> 636 | struct uffdio_move uffdio_move;
> | ^~~~~~~~~~~
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-08 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 10:00 kernel test robot
2023-12-08 17:27 ` Suren Baghdasaryan [this message]
2023-12-08 18:05 ` Andrew Morton
2023-12-08 18:06 ` Suren Baghdasaryan
2023-12-08 18:09 ` Suren Baghdasaryan
2023-12-08 18:14 ` Andrew Morton
2023-12-08 22:17 ` Suren Baghdasaryan
2023-12-08 18:06 ` Suren Baghdasaryan
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='CAJuCfpF_FN07Pvn5BJn1vJMAeEPKRBdfT3kWXVD=WAfizto+UQ@mail.gmail.com' \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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