From: Peter Xu <peterx@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 5085/5845] fs/userfaultfd.c:337:13: error: implicit declaration of function 'pte_none_mostly'
Date: Sat, 23 Apr 2022 16:45:10 -0400 [thread overview]
Message-ID: <YmRlVj3cdizYJsr0@xz-m1.local> (raw)
In-Reply-To: <202204240320.TGDuGcsL-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]
On Sun, Apr 24, 2022 at 03:23:23AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: e7d6987e09a328d4a949701db40ef63fbb970670
> commit: 70a8da53f7cb7368776f9d2790ecbb4f8bc53ba5 [5085/5845] mm: teach core mm about pte markers
> config: x86_64-randconfig-a002-20210928 (https://download.01.org/0day-ci/archive/20220424/202204240320.TGDuGcsL-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
> reproduce (this is a W=1 build):
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=70a8da53f7cb7368776f9d2790ecbb4f8bc53ba5
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 70a8da53f7cb7368776f9d2790ecbb4f8bc53ba5
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> Note: the linux-next/master HEAD e7d6987e09a328d4a949701db40ef63fbb970670 builds fine.
> It may have been fixed somewhere.
>
> All errors (new ones prefixed by >>):
>
> fs/userfaultfd.c: In function 'userfaultfd_must_wait':
> >> fs/userfaultfd.c:337:13: error: implicit declaration of function 'pte_none_mostly' [-Werror=implicit-function-declaration]
> 337 | if (pte_none_mostly(*pte))
> | ^~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
Ah, userfaultfd.c may need explicit inclusion for swapops.h now.. Expected
fix attached to be squashed into "mm: Teach core mm about pte markers", I think.
Thanks,
--
Peter Xu
[-- Attachment #2: 0001-fixup-mm-Teach-core-mm-about-pte-markers.patch --]
[-- Type: text/plain, Size: 667 bytes --]
From 009572e59f7d72c5085676b0506f0b269f9ef334 Mon Sep 17 00:00:00 2001
From: Peter Xu <peterx@redhat.com>
Date: Sat, 23 Apr 2022 16:39:15 -0400
Subject: [PATCH] fixup! mm: Teach core mm about pte markers
Content-type: text/plain
Signed-off-by: Peter Xu <peterx@redhat.com>
---
fs/userfaultfd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
index fb45522a2b44..e943370107d0 100644
--- a/fs/userfaultfd.c
+++ b/fs/userfaultfd.c
@@ -29,6 +29,7 @@
#include <linux/ioctl.h>
#include <linux/security.h>
#include <linux/hugetlb.h>
+#include <linux/swapops.h>
int sysctl_unprivileged_userfaultfd __read_mostly;
--
2.32.0
prev parent reply other threads:[~2022-04-23 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 19:23 kernel test robot
2022-04-23 20:45 ` Peter Xu [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=YmRlVj3cdizYJsr0@xz-m1.local \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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