From: kernel test robot <lkp@intel.com>
To: Omar Sandoval <osandov@fb.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [hnaz-mm:master 16/188] mm/vmalloc.c:1747:6: warning: no previous prototype for 'iounmap_purge_vmap_area'
Date: Wed, 6 Apr 2022 10:42:25 +0800 [thread overview]
Message-ID: <202204061005.jSc4B5gA-lkp@intel.com> (raw)
tree: https://github.com/hnaz/linux-mm master
head: 71e0d841ccd1c91e7038d385825e26342e87d198
commit: 56de161065643707f3a3a0fd0cc2c9e747148eae [16/188] mm/vmalloc: fix spinning drain_vmap_work after reading from /proc/vmcore
config: um-x86_64_defconfig (https://download.01.org/0day-ci/archive/20220406/202204061005.jSc4B5gA-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-19) 11.2.0
reproduce (this is a W=1 build):
# https://github.com/hnaz/linux-mm/commit/56de161065643707f3a3a0fd0cc2c9e747148eae
git remote add hnaz-mm https://github.com/hnaz/linux-mm
git fetch --no-tags hnaz-mm master
git checkout 56de161065643707f3a3a0fd0cc2c9e747148eae
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=um SUBARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> mm/vmalloc.c:1747:6: warning: no previous prototype for 'iounmap_purge_vmap_area' [-Wmissing-prototypes]
1747 | void iounmap_purge_vmap_area(void)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/iounmap_purge_vmap_area +1747 mm/vmalloc.c
1744
1745 #ifdef CONFIG_X86_64
1746 /* Called after iounmap() to immediately free vm_area_struct's. */
> 1747 void iounmap_purge_vmap_area(void)
1748 {
1749 mutex_lock(&vmap_purge_lock);
1750 __purge_vmap_area_lazy(ULONG_MAX, 0);
1751 mutex_unlock(&vmap_purge_lock);
1752 }
1753 #endif /* CONFIG_X86_64 */
1754
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-06 2:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202204061005.jSc4B5gA-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osandov@fb.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