From: Suren Baghdasaryan <surenb@google.com>
To: kernel test robot <lkp@intel.com>
Cc: akpm@linux-foundation.org, oe-kbuild-all@lists.linux.dev,
kent.overstreet@linux.dev, vbabka@suse.cz, harry.yoo@oracle.com,
da.gomez@kernel.org, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/1] alloc_tag: skip rcu barrier on module unload if profiling was not enabled
Date: Tue, 9 Dec 2025 06:30:58 +0900 [thread overview]
Message-ID: <CAJuCfpGkdz7QhOGuS2SSTw09FrQkQLPFpQuLtMkmFAbJhGGbKQ@mail.gmail.com> (raw)
In-Reply-To: <202512061207.7zufoIcC-lkp@intel.com>
On Sat, Dec 6, 2025 at 2:08 PM kernel test robot <lkp@intel.com> wrote:
>
> Hi Suren,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on 3f43be96f919cc611dcb2a4e38dd464831f4513e]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Suren-Baghdasaryan/alloc_tag-skip-rcu-barrier-on-module-unload-if-profiling-was-not-enabled/20251205-061310
> base: 3f43be96f919cc611dcb2a4e38dd464831f4513e
> patch link: https://lore.kernel.org/r/20251204220957.360838-1-surenb%40google.com
> patch subject: [PATCH 1/1] alloc_tag: skip rcu barrier on module unload if profiling was not enabled
> config: parisc-randconfig-002-20251206 (https://download.01.org/0day-ci/archive/20251206/202512061207.7zufoIcC-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 15.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251206/202512061207.7zufoIcC-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/202512061207.7zufoIcC-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> lib/codetag.c:37:13: warning: 'flush_rcu_on_module_unload' defined but not used [-Wunused-variable]
> 37 | static bool flush_rcu_on_module_unload;
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks! I'll fix it and repost after Plumbers as the original issue
seems to be resolved by Harry's patches and this optimization is not
urgent anymore.
>
>
> vim +/flush_rcu_on_module_unload +37 lib/codetag.c
>
> 34
> 35 static DEFINE_MUTEX(codetag_lock);
> 36 static LIST_HEAD(codetag_types);
> > 37 static bool flush_rcu_on_module_unload;
> 38
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-12-08 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 22:09 Suren Baghdasaryan
2025-12-06 4:45 ` kernel test robot
2025-12-06 5:08 ` kernel test robot
2025-12-08 21:30 ` 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=CAJuCfpGkdz7QhOGuS2SSTw09FrQkQLPFpQuLtMkmFAbJhGGbKQ@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=da.gomez@kernel.org \
--cc=harry.yoo@oracle.com \
--cc=jonathanh@nvidia.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vbabka@suse.cz \
/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