From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:bcachefs-testing 110/113] fs/bcachefs/btree_cache.c:190:22: warning: unused variable 'bc'
Date: Fri, 4 Jul 2025 05:22:29 +0200 [thread overview]
Message-ID: <202507040501.Ap74GJO2-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs bcachefs-testing
head: 869fe6267c3286b53f85effa38ab83a6200fd49b
commit: ace9e99ba674c601f71218613ecfec44976becfc [110/113] bcachefs: Tweak btree cache helpers for use by btree node scan
config: arc-randconfig-2002-20250704 (https://download.01.org/0day-ci/archive/20250704/202507040501.Ap74GJO2-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250704/202507040501.Ap74GJO2-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/202507040501.Ap74GJO2-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/bcachefs/btree_cache.c: In function '__bch2_btree_node_mem_alloc':
>> fs/bcachefs/btree_cache.c:190:22: warning: unused variable 'bc' [-Wunused-variable]
190 | struct btree_cache *bc = &c->btree_cache;
| ^~
vim +/bc +190 fs/bcachefs/btree_cache.c
4580baec7fbee2 Kent Overstreet 2020-07-25 187
6adaac0b95dd39 Kent Overstreet 2021-04-20 188 struct btree *__bch2_btree_node_mem_alloc(struct bch_fs *c)
4580baec7fbee2 Kent Overstreet 2020-07-25 189 {
4580baec7fbee2 Kent Overstreet 2020-07-25 @190 struct btree_cache *bc = &c->btree_cache;
a10195764901e0 Kent Overstreet 2022-10-22 191 struct btree *b;
a10195764901e0 Kent Overstreet 2022-10-22 192
a10195764901e0 Kent Overstreet 2022-10-22 193 b = __btree_node_mem_alloc(c, GFP_KERNEL);
4580baec7fbee2 Kent Overstreet 2020-07-25 194 if (!b)
4580baec7fbee2 Kent Overstreet 2020-07-25 195 return NULL;
1c6fdbd8f2465d Kent Overstreet 2017-03-16 196
4580baec7fbee2 Kent Overstreet 2020-07-25 197 if (btree_node_data_alloc(c, b, GFP_KERNEL)) {
4580baec7fbee2 Kent Overstreet 2020-07-25 198 kfree(b);
4580baec7fbee2 Kent Overstreet 2020-07-25 199 return NULL;
4580baec7fbee2 Kent Overstreet 2020-07-25 200 }
4580baec7fbee2 Kent Overstreet 2020-07-25 201
677bdb7346b6fd Alan Huang 2025-02-26 202 bch2_btree_lock_init(&b->c, 0, GFP_KERNEL);
4580baec7fbee2 Kent Overstreet 2020-07-25 203 return b;
1c6fdbd8f2465d Kent Overstreet 2017-03-16 204 }
1c6fdbd8f2465d Kent Overstreet 2017-03-16 205
:::::: The code at line 190 was first introduced by commit
:::::: 4580baec7fbee2fdceb9b5b2b337ea3734a6d2b8 bcachefs: Remove some uses of PAGE_SIZE in the btree code
:::::: TO: Kent Overstreet <kent.overstreet@gmail.com>
:::::: CC: Kent Overstreet <kent.overstreet@linux.dev>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-04 3:22 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=202507040501.Ap74GJO2-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.