From: kernel test robot <lkp@intel.com>
To: Chengming Zhou <zhouchengming@bytedance.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [linux-next:master 10516/10830] mm/zsmalloc.c:742:23: warning: 'get_zspage_lockless' defined but not used
Date: Wed, 28 Feb 2024 23:10:19 +0800 [thread overview]
Message-ID: <202402282356.8HzbImAg-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 20af1ca418d2c0b11bc2a1fe8c0c88f67bcc2a7e
commit: 2258bdebb55e3ad3d30fd3849ddb955ff36825de [10516/10830] mm/zsmalloc: don't hold locks of all pages when free_zspage()
config: m68k-hp300_defconfig (https://download.01.org/0day-ci/archive/20240228/202402282356.8HzbImAg-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240228/202402282356.8HzbImAg-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/202402282356.8HzbImAg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/zsmalloc.c:742:23: warning: 'get_zspage_lockless' defined but not used [-Wunused-function]
742 | static struct zspage *get_zspage_lockless(struct page *page)
| ^~~~~~~~~~~~~~~~~~~
mm/zsmalloc.c:288:13: warning: 'kick_deferred_free' defined but not used [-Wunused-function]
288 | static void kick_deferred_free(struct zs_pool *pool) {}
| ^~~~~~~~~~~~~~~~~~
vim +/get_zspage_lockless +742 mm/zsmalloc.c
740
741 /* Only used in zs_page_migrate() to get zspage locklessly. */
> 742 static struct zspage *get_zspage_lockless(struct page *page)
743 {
744 struct zspage __rcu **private = (struct zspage __rcu **)&page->private;
745
746 return rcu_dereference(*private);
747 }
748
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-02-28 15:11 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=202402282356.8HzbImAg-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=zhouchengming@bytedance.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