From: Suren Baghdasaryan <surenb@google.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: mm/slub.c:2077:1: error: unused function 'prepare_slab_obj_exts_hook'
Date: Thu, 11 Jul 2024 10:09:13 -0700 [thread overview]
Message-ID: <CAJuCfpEwNE5tsm+iZTzZc-hdR5sBXAKd57tOGum67_fAu2Gi3A@mail.gmail.com> (raw)
In-Reply-To: <202407050845.zNONqauD-lkp@intel.com>
On Thu, Jul 4, 2024 at 5:35 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 661e504db04c6b7278737ee3a9116738536b4ed4
> commit: b4601d096aac8ed26afa88ef8b249975b0530ca1 mm/slab: fix 'variable obj_exts set but not used' warning
> date: 10 days ago
> config: x86_64-sof-customedconfig-amd-defconfig (https://download.01.org/0day-ci/archive/20240705/202407050845.zNONqauD-lkp@intel.com/config)
> compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240705/202407050845.zNONqauD-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/202407050845.zNONqauD-lkp@intel.com/
Fix is posted at
https://lore.kernel.org/all/20240711170216.1149695-1-surenb@google.com/
over slab/for-next baseline because that branch contains another code
refactoring [1] which would cause merge conflicts.
[1] https://lore.kernel.org/all/20240704135941.1145038-1-surenb@google.com/
>
> All errors (new ones prefixed by >>):
>
> >> mm/slub.c:2077:1: error: unused function 'prepare_slab_obj_exts_hook' [-Werror,-Wunused-function]
> 2077 | prepare_slab_obj_exts_hook(struct kmem_cache *s, gfp_t flags, void *p)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> 1 error generated.
>
>
> vim +/prepare_slab_obj_exts_hook +2077 mm/slub.c
>
> 0bedcc66d2a43a Vlastimil Babka 2023-10-03 2075
> 4b8736964640fe Suren Baghdasaryan 2024-03-21 2076 static inline struct slabobj_ext *
> 4b8736964640fe Suren Baghdasaryan 2024-03-21 @2077 prepare_slab_obj_exts_hook(struct kmem_cache *s, gfp_t flags, void *p)
> 3450a0e5a6fc4c Vlastimil Babka 2023-11-13 2078 {
> 4b8736964640fe Suren Baghdasaryan 2024-03-21 2079 return NULL;
> 4b8736964640fe Suren Baghdasaryan 2024-03-21 2080 }
> 3450a0e5a6fc4c Vlastimil Babka 2023-11-13 2081
>
> :::::: The code at line 2077 was first introduced by commit
> :::::: 4b8736964640fe160724e7135dc62883bddcdace mm/slab: add allocation accounting into slab allocation and free paths
>
> :::::: TO: Suren Baghdasaryan <surenb@google.com>
> :::::: CC: Andrew Morton <akpm@linux-foundation.org>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-07-11 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 0:35 kernel test robot
2024-07-11 17:09 ` Suren Baghdasaryan [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=CAJuCfpEwNE5tsm+iZTzZc-hdR5sBXAKd57tOGum67_fAu2Gi3A@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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