From: Coly Li <colyli@suse.de>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: oe-kbuild@lists.linux.dev, Zheng Wang <zyytlz.wz@163.com>,
lkp@intel.com, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: drivers/md/bcache/btree.c:1511 btree_gc_rewrite_node() error: 'n' dereferencing possible ERR_PTR()
Date: Tue, 7 Nov 2023 14:34:38 +0800 [thread overview]
Message-ID: <6AAB7139-DE98-49BC-9DF9-F1819A39795E@suse.de> (raw)
In-Reply-To: <a754f8a3-cbfb-42bb-b776-94ecac062daf@kadam.mountain>
> 2023年11月6日 17:11,Dan Carpenter <dan.carpenter@linaro.org> 写道:
>
> Hi Zheng,
>
> FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 77fa2fbe87fc605c4bfa87dff87be9bfded0e9a3
> commit: 028ddcac477b691dd9205c92f991cc15259d033e bcache: Remove unnecessary NULL point check in node allocations
> config: x86_64-randconfig-161-20231102 (https://download.01.org/0day-ci/archive/20231106/202311060857.2jHVe0uk-lkp@intel.com/config)
> compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
> reproduce: (https://download.01.org/0day-ci/archive/20231106/202311060857.2jHVe0uk-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>
> | Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> | Closes: https://lore.kernel.org/r/202311060857.2jHVe0uk-lkp@intel.com/
>
> New smatch warnings:
> drivers/md/bcache/btree.c:1511 btree_gc_rewrite_node() error: 'n' dereferencing possible ERR_PTR()
>
> Old smatch warnings:
> drivers/md/bcache/btree.c:1527 btree_gc_rewrite_node() error: 'n' dereferencing possible ERR_PTR()
>
> vim +/n +1511 drivers/md/bcache/btree.c
>
> 0a63b66db566cf Kent Overstreet 2014-03-17 1497 static int btree_gc_rewrite_node(struct btree *b, struct btree_op *op,
> 0a63b66db566cf Kent Overstreet 2014-03-17 1498 struct btree *replace)
> 0a63b66db566cf Kent Overstreet 2014-03-17 1499 {
> 0a63b66db566cf Kent Overstreet 2014-03-17 1500 struct keylist keys;
> 0a63b66db566cf Kent Overstreet 2014-03-17 1501 struct btree *n;
> 0a63b66db566cf Kent Overstreet 2014-03-17 1502
> 0a63b66db566cf Kent Overstreet 2014-03-17 1503 if (btree_check_reserve(b, NULL))
> 0a63b66db566cf Kent Overstreet 2014-03-17 1504 return 0;
> 0a63b66db566cf Kent Overstreet 2014-03-17 1505
> 0a63b66db566cf Kent Overstreet 2014-03-17 1506 n = btree_node_alloc_replacement(replace, NULL);
>
> Needs some error handling. I don't know why the zero day bot is
> sending repeat warnings today but this one is still worth fixing.
> I guess the zero day bot sent the previous warning to the wrong people
> last time.
Yes this is a valid report. I feel checking n after btree_node_alloc_replacement() is necessary, and recent change from Zheng exported this potential issue to static code checking tool.
Since Zheng doesn’t respond yet, I will post a patch to fix the potential issue.
Thanks.
Coly Li
>
> https://lore.kernel.org/all/bab6966d-3f96-44a0-b666-ddf976179eab@kadam.mountain/
>
> 0a63b66db566cf Kent Overstreet 2014-03-17 1507
> 0a63b66db566cf Kent Overstreet 2014-03-17 1508 /* recheck reserve after allocating replacement node */
> 0a63b66db566cf Kent Overstreet 2014-03-17 1509 if (btree_check_reserve(b, NULL)) {
> 0a63b66db566cf Kent Overstreet 2014-03-17 1510 btree_node_free(n);
> 0a63b66db566cf Kent Overstreet 2014-03-17 @1511 rw_unlock(true, n);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1512 return 0;
> 0a63b66db566cf Kent Overstreet 2014-03-17 1513 }
> 0a63b66db566cf Kent Overstreet 2014-03-17 1514
> 0a63b66db566cf Kent Overstreet 2014-03-17 1515 bch_btree_node_write_sync(n);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1516
> 0a63b66db566cf Kent Overstreet 2014-03-17 1517 bch_keylist_init(&keys);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1518 bch_keylist_add(&keys, &n->key);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1519
> 0a63b66db566cf Kent Overstreet 2014-03-17 1520 make_btree_freeing_key(replace, keys.top);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1521 bch_keylist_push(&keys);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1522
> 0a63b66db566cf Kent Overstreet 2014-03-17 1523 bch_btree_insert_node(b, op, &keys, NULL, NULL);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1524 BUG_ON(!bch_keylist_empty(&keys));
> 0a63b66db566cf Kent Overstreet 2014-03-17 1525
> 0a63b66db566cf Kent Overstreet 2014-03-17 1526 btree_node_free(replace);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1527 rw_unlock(true, n);
> 0a63b66db566cf Kent Overstreet 2014-03-17 1528
> 0a63b66db566cf Kent Overstreet 2014-03-17 1529 /* Invalidated our iterator */
> 0a63b66db566cf Kent Overstreet 2014-03-17 1530 return -EINTR;
> 0a63b66db566cf Kent Overstreet 2014-03-17 1531 }
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2023-11-07 6:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 9:11 Dan Carpenter
2023-11-07 6:34 ` Coly Li [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=6AAB7139-DE98-49BC-9DF9-F1819A39795E@suse.de \
--to=colyli@suse.de \
--cc=axboe@kernel.dk \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=zyytlz.wz@163.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
all inboxes | Powered by JetHome®