From: Lorenzo Stoakes <lstoakes@gmail.com>
To: kernel test robot <lkp@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jason Gunthorpe <jgg@ziepe.ca>, Jens Axboe <axboe@kernel.dk>,
Matthew Wilcox <willy@infradead.org>,
Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
Leon Romanovsky <leon@kernel.org>,
Christian Benvenuti <benve@cisco.com>,
Nelson Escobar <neescoba@cisco.com>,
Bernard Metzler <bmt@zurich.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Bjorn Topel <bjorn@kernel.org>,
Magnus Karlsson <magnus.karlsson@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH v6 3/3] mm/gup: disallow FOLL_LONGTERM GUP-fast writing to file-backed mappings
Date: Tue, 2 May 2023 08:46:33 +0100 [thread overview]
Message-ID: <db733020-c6c7-43f9-9cbf-0e5fb18b2f01@lucifer.local> (raw)
In-Reply-To: <202305021142.vBYXxxEh-lkp@intel.com>
On Tue, May 02, 2023 at 11:33:29AM +0800, kernel test robot wrote:
> Hi Lorenzo,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on akpm-mm/mm-everything]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Stoakes/mm-mmap-separate-writenotify-and-dirty-tracking-logic/20230502-071520
> base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link: https://lore.kernel.org/r/dee4f4ad6532b0f94d073da263526de334d5d7e0.1682981880.git.lstoakes%40gmail.com
> patch subject: [PATCH v6 3/3] mm/gup: disallow FOLL_LONGTERM GUP-fast writing to file-backed mappings
> config: arm-randconfig-r013-20230502 (https://download.01.org/0day-ci/archive/20230502/202305021142.vBYXxxEh-lkp@intel.com/config)
> compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project b1465cd49efcbc114a75220b153f5a055ce7911f)
> 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
> # install arm cross compiling tool for clang build
> # apt-get install binutils-arm-linux-gnueabi
> # https://github.com/intel-lab-lkp/linux/commit/602bb9fab888bd9176b8eeb80a0da68499c343ed
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review Lorenzo-Stoakes/mm-mmap-separate-writenotify-and-dirty-tracking-logic/20230502-071520
> git checkout 602bb9fab888bd9176b8eeb80a0da68499c343ed
> # 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=arm olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202305021142.vBYXxxEh-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> mm/gup.c:114:49: warning: omitting the parameter name in a function definition is a C2x extension [-Wc2x-extensions]
> static bool stabilise_mapping_rcu(struct folio *)
> ^
> 1 warning generated.
>
>
> vim +114 mm/gup.c
>
> 108
> 109 static void unlock_rcu(void)
> 110 {
> 111 rcu_read_unlock();
> 112 }
> 113 #else
> > 114 static bool stabilise_mapping_rcu(struct folio *)
> 115 {
> 116 return true;
> 117 }
> 118
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests
Am slightly surprised that's a C2x extension :)
-fix patch attached
----8<----
From 829cb87ddd84e4496310b12d26e65de11d5b9e53 Mon Sep 17 00:00:00 2001
From: Lorenzo Stoakes <lstoakes@gmail.com>
Date: Tue, 2 May 2023 08:40:48 +0100
Subject: [PATCH] mm/gup: disallow FOLL_LONGTERM GUP-fast writing to
file-backed mappings
Fix compiler warning.
Signed-off-by: Lorenzo Stoakes <lstoakes@gmail.com>
---
mm/gup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/gup.c b/mm/gup.c
index 431618048a03..ffc3caf120fc 100644
--- a/mm/gup.c
+++ b/mm/gup.c
@@ -111,7 +111,7 @@ static void unlock_rcu(void)
rcu_read_unlock();
}
#else
-static bool stabilise_mapping_rcu(struct folio *)
+static bool stabilise_mapping_rcu(struct folio *folio)
{
return true;
}
--
2.40.1
next prev parent reply other threads:[~2023-05-02 14:58 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 23:11 [PATCH v6 0/3] mm/gup: disallow GUP writing to file-backed mappings by default Lorenzo Stoakes
2023-05-01 23:11 ` [PATCH v6 1/3] mm/mmap: separate writenotify and dirty tracking logic Lorenzo Stoakes
2023-05-01 23:11 ` [PATCH v6 2/3] mm/gup: disallow FOLL_LONGTERM GUP-nonfast writing to file-backed mappings Lorenzo Stoakes
2023-05-02 15:04 ` David Hildenbrand
2023-05-02 15:17 ` Lorenzo Stoakes
2023-05-01 23:11 ` [PATCH v6 3/3] mm/gup: disallow FOLL_LONGTERM GUP-fast " Lorenzo Stoakes
2023-05-01 23:42 ` John Hubbard
[not found] ` <202305021142.vBYXxxEh-lkp@intel.com>
2023-05-02 7:46 ` Lorenzo Stoakes [this message]
2023-05-02 11:13 ` Peter Zijlstra
2023-05-02 11:23 ` Jan Kara
2023-05-02 11:25 ` Lorenzo Stoakes
2023-05-02 11:28 ` Lorenzo Stoakes
2023-05-02 12:08 ` Peter Zijlstra
2023-05-02 12:27 ` Lorenzo Stoakes
2023-05-02 12:40 ` Peter Zijlstra
2023-05-02 12:47 ` David Hildenbrand
2023-05-02 12:52 ` Lorenzo Stoakes
2023-05-02 13:30 ` Paul E. McKenney
2023-05-02 11:20 ` Jan Kara
2023-05-02 12:46 ` Christian Borntraeger
2023-05-02 12:54 ` Lorenzo Stoakes
2023-05-02 13:02 ` Jason Gunthorpe
2023-05-02 13:04 ` Christian Borntraeger
2023-05-02 13:10 ` Jason Gunthorpe
2023-05-02 13:28 ` David Hildenbrand
2023-05-02 13:36 ` Jason Gunthorpe
2023-05-02 13:39 ` David Hildenbrand
2023-05-02 13:43 ` Matthew Rosato
2023-05-02 13:47 ` David Hildenbrand
2023-05-02 13:50 ` Jason Gunthorpe
2023-05-02 13:56 ` Matthew Rosato
2023-05-02 15:09 ` David Hildenbrand
2023-05-02 15:19 ` Lorenzo Stoakes
2023-05-02 15:20 ` Matthew Rosato
2023-05-02 13:57 ` David Hildenbrand
2023-05-02 14:04 ` Jason Gunthorpe
2023-05-02 14:15 ` David Hildenbrand
2023-05-02 14:54 ` Matthew Rosato
2023-05-02 15:20 ` Jason Gunthorpe
2023-05-02 15:32 ` Peter Xu
2023-05-02 15:36 ` Jason Gunthorpe
2023-05-02 15:45 ` David Hildenbrand
2023-05-02 16:06 ` Jason Gunthorpe
2023-05-02 16:12 ` David Hildenbrand
2023-05-02 16:19 ` Jason Gunthorpe
2023-05-02 16:32 ` David Hildenbrand
2023-05-02 17:46 ` Jason Gunthorpe
2023-05-02 17:59 ` Matthew Rosato
2023-05-02 18:09 ` Jason Gunthorpe
2023-05-02 19:23 ` David Hildenbrand
2023-05-02 13:38 ` Matthew Rosato
2023-05-02 13:35 ` Matthew Rosato
2023-05-02 14:57 ` David Hildenbrand
2023-05-02 15:19 ` Matthew Rosato
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=db733020-c6c7-43f9-9cbf-0e5fb18b2f01@lucifer.local \
--to=lstoakes@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=axboe@kernel.dk \
--cc=benve@cisco.com \
--cc=bjorn@kernel.org \
--cc=bmt@zurich.ibm.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=edumazet@google.com \
--cc=irogers@google.com \
--cc=jgg@ziepe.ca \
--cc=jolsa@kernel.org \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=neescoba@cisco.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=willy@infradead.org \
/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