From: Peter Xu <peterx@redhat.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 6398/6705] mm/page_table_check.c:194:1: warning: control reaches end of non-void function
Date: Wed, 17 Apr 2024 12:54:36 -0400 [thread overview]
Message-ID: <Zh_-zHKPMp564sAG@x1n> (raw)
In-Reply-To: <202404171745.Zd13ydca-lkp@intel.com>
On Wed, Apr 17, 2024 at 06:01:49PM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 4eab358930711bbeb85bf5ee267d0d42d3394c2c
> commit: 62754e4df9e04c4576e989f5ea2b909e824d8164 [6398/6705] mm/page_table_check: support userfault wr-protect entries
> config: riscv-randconfig-r001-20230105 (https://download.01.org/0day-ci/archive/20240417/202404171745.Zd13ydca-lkp@intel.com/config)
> compiler: riscv64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240417/202404171745.Zd13ydca-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/202404171745.Zd13ydca-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> mm/page_table_check.c: In function 'swap_cached_writable':
> mm/page_table_check.c:192:24: error: 'SWP_DEVICE_EXCLUSIVE_WRITE' undeclared (first use in this function)
> 192 | return type == SWP_DEVICE_EXCLUSIVE_WRITE ||
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> mm/page_table_check.c:192:24: note: each undeclared identifier is reported only once for each function it appears in
> >> mm/page_table_check.c:194:1: warning: control reaches end of non-void function [-Wreturn-type]
> 194 | }
> | ^
>
>
> vim +194 mm/page_table_check.c
>
> 186
> 187 /* Whether the swap entry cached writable information */
> 188 static inline bool swap_cached_writable(swp_entry_t entry)
> 189 {
> 190 unsigned type = swp_type(entry);
> 191
> 192 return type == SWP_DEVICE_EXCLUSIVE_WRITE ||
> 193 type == SWP_MIGRATION_WRITE;
> > 194 }
> 195
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
I'll send a v2 of this patch soon to fix all these issues, after I check
with Pasha on some other changes.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2024-04-17 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 10:01 kernel test robot
2024-04-17 16:54 ` 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=Zh_-zHKPMp564sAG@x1n \
--to=peterx@redhat.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