From: kernel test robot <lkp@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Tom Zanussi <zanussi@kernel.org>
Subject: [cip:linux-4.19.y-cip-rt-rebase 2065/9999] net/xfrm/xfrm_ipcomp.c:40:30: warning: 'ipcomp_scratches_lock' defined but not used
Date: Fri, 17 Jun 2022 14:27:17 +0800 [thread overview]
Message-ID: <202206171457.YUwoAiZH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git linux-4.19.y-cip-rt-rebase
head: 4784425d57541175db8c44ceef091a8fb42e5c6f
commit: ad01e51437422285ac98eced7c7136b368bd2ffc [2065/9999] net: xfrm: fix compress vs decompress serialization
config: x86_64-randconfig-a015 (https://download.01.org/0day-ci/archive/20220617/202206171457.YUwoAiZH-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?id=ad01e51437422285ac98eced7c7136b368bd2ffc
git remote add cip https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
git fetch --no-tags cip linux-4.19.y-cip-rt-rebase
git checkout ad01e51437422285ac98eced7c7136b368bd2ffc
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash net/xfrm/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from net/xfrm/xfrm_ipcomp.c:23:
>> net/xfrm/xfrm_ipcomp.c:40:30: warning: 'ipcomp_scratches_lock' defined but not used [-Wunused-const-variable=]
40 | static DEFINE_LOCAL_IRQ_LOCK(ipcomp_scratches_lock);
| ^~~~~~~~~~~~~~~~~~~~~
include/linux/locallock.h:244:71: note: in definition of macro 'DEFINE_LOCAL_IRQ_LOCK'
244 | #define DEFINE_LOCAL_IRQ_LOCK(lvar) __typeof__(const int) lvar
| ^~~~
vim +/ipcomp_scratches_lock +40 net/xfrm/xfrm_ipcomp.c
> 23 #include <linux/locallock.h>
24 #include <linux/percpu.h>
25 #include <linux/slab.h>
26 #include <linux/smp.h>
27 #include <linux/vmalloc.h>
28 #include <net/ip.h>
29 #include <net/ipcomp.h>
30 #include <net/xfrm.h>
31
32 struct ipcomp_tfms {
33 struct list_head list;
34 struct crypto_comp * __percpu *tfms;
35 int users;
36 };
37
38 static DEFINE_MUTEX(ipcomp_resource_mutex);
39 static void * __percpu *ipcomp_scratches;
> 40 static DEFINE_LOCAL_IRQ_LOCK(ipcomp_scratches_lock);
41 static int ipcomp_scratch_users;
42 static LIST_HEAD(ipcomp_tfms_list);
43
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-17 6:27 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=202206171457.YUwoAiZH-lkp@intel.com \
--to=lkp@intel.com \
--cc=dave@stgolabs.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zanussi@kernel.org \
/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
all inboxes | Powered by JetHome®