From: kernel test robot <lkp@intel.com>
To: Alexandr Sapozhnkiov <alsp705@gmail.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Alexandr Sapozhnikov <alsp705@gmail.com>,
linux-media@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 5.10] md: fix NULL pointer dereference at reregister_snapshot()
Date: Tue, 23 Sep 2025 14:05:41 +0800 [thread overview]
Message-ID: <202509231318.YYdqPhnu-lkp@intel.com> (raw)
In-Reply-To: <20250922144239.11-1-alsp705@gmail.com>
Hi Alexandr,
kernel test robot noticed the following build warnings:
[auto build test WARNING on device-mapper-dm/for-next]
[also build test WARNING on linus/master v6.17-rc7 next-20250922]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Alexandr-Sapozhnkiov/md-fix-NULL-pointer-dereference-at-reregister_snapshot/20250922-224522
base: https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
patch link: https://lore.kernel.org/r/20250922144239.11-1-alsp705%40gmail.com
patch subject: [PATCH 5.10] md: fix NULL pointer dereference at reregister_snapshot()
config: s390-randconfig-002-20250923 (https://download.01.org/0day-ci/archive/20250923/202509231318.YYdqPhnu-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project cafc064fc7a96b3979a023ddae1da2b499d6c954)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250923/202509231318.YYdqPhnu-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/202509231318.YYdqPhnu-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from <built-in>:3:
In file included from include/linux/compiler_types.h:171:
include/linux/compiler-clang.h:28:9: warning: '__SANITIZE_ADDRESS__' macro redefined [-Wmacro-redefined]
28 | #define __SANITIZE_ADDRESS__
| ^
<built-in>:369:9: note: previous definition is here
369 | #define __SANITIZE_ADDRESS__ 1
| ^
>> drivers/md/dm-snap.c:597:23: warning: unused variable 'bdev' [-Wunused-variable]
597 | struct block_device *bdev = s->origin->bdev;
| ^~~~
2 warnings generated.
vim +/bdev +597 drivers/md/dm-snap.c
c1f0c183f6acc6 Mike Snitzer 2009-12-10 590
c1f0c183f6acc6 Mike Snitzer 2009-12-10 591 /*
c1f0c183f6acc6 Mike Snitzer 2009-12-10 592 * Move snapshot to correct place in list according to chunk size.
c1f0c183f6acc6 Mike Snitzer 2009-12-10 593 */
c1f0c183f6acc6 Mike Snitzer 2009-12-10 594 static void reregister_snapshot(struct dm_snapshot *s)
c1f0c183f6acc6 Mike Snitzer 2009-12-10 595 {
8125cedd7aa81d Alexandr Sapozhnikov 2025-09-22 596 struct origin *o;
c1f0c183f6acc6 Mike Snitzer 2009-12-10 @597 struct block_device *bdev = s->origin->bdev;
c1f0c183f6acc6 Mike Snitzer 2009-12-10 598
c1f0c183f6acc6 Mike Snitzer 2009-12-10 599 down_write(&_origins_lock);
8125cedd7aa81d Alexandr Sapozhnikov 2025-09-22 600 o = __lookup_origin(s->origin->bdev);
c1f0c183f6acc6 Mike Snitzer 2009-12-10 601
c1f0c183f6acc6 Mike Snitzer 2009-12-10 602 list_del(&s->list);
8125cedd7aa81d Alexandr Sapozhnikov 2025-09-22 603 if (o)
8125cedd7aa81d Alexandr Sapozhnikov 2025-09-22 604 __insert_snapshot(o, s);
^1da177e4c3f41 Linus Torvalds 2005-04-16 605
^1da177e4c3f41 Linus Torvalds 2005-04-16 606 up_write(&_origins_lock);
^1da177e4c3f41 Linus Torvalds 2005-04-16 607 }
^1da177e4c3f41 Linus Torvalds 2005-04-16 608
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-23 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 14:42 [PATCH 5.10] md: fix NULL pointer dereference at reregister_snapshot() Alexandr Sapozhnkiov
2025-09-23 6:05 ` kernel test robot [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=202509231318.YYdqPhnu-lkp@intel.com \
--to=lkp@intel.com \
--cc=agk@redhat.com \
--cc=alsp705@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lvc-project@linuxtesting.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=snitzer@redhat.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 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.