From: kernel test robot <oliver.sang@intel.com>
To: Daan De Meyer <daan.j.demeyer@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
Daan De Meyer <daan@amutable.com>,
"Christian Brauner" <brauner@kernel.org>,
<linux-block@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [loop] 267ec4d722: blktests.loop/009.fail
Date: Wed, 15 Jul 2026 14:02:40 +0800 [thread overview]
Message-ID: <202607150754.b660f5b9-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "blktests.loop/009.fail" on:
commit: 267ec4d7223a783f029a980f41b93c39b17996da ("loop: fix partition scan race between udev and loop_reread_partitions()")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 4a50a141f05a8d1737661b19ee22ff8455b94409]
[test failed on linux-next/master 4f441960e691d37c880d2cc004de06bb5b6bd5e4]
in testcase: blktests
version: blktests-x86_64-5a62429-1_20260623
with following parameters:
test: loop-group-00
config: x86_64-rhel-9.4-func
compiler: gcc-14
test machine: 16 threads Intel(R) Core(TM) i7-13620H (Raptor Lake) with 32G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202607150754.b660f5b9-lkp@intel.com
2026-07-09 09:47:14 cd /lkp/benchmarks/blktests
2026-07-09 09:47:14 sed "s:^:loop/:" /lkp/benchmarks/blktests/tests/loop-group-00
2026-07-09 09:47:14 ./check loop/001 loop/002 loop/003 loop/004 loop/005 loop/006 loop/007 loop/008 loop/009 loop/010 loop/011 loop/012
...
loop/009 (check that LOOP_CONFIGURE sends uevents for partitions)
loop/009 (check that LOOP_CONFIGURE sends uevents for partitions) [failed]
runtime ... 5.282s
--- tests/loop/009.out 2026-06-23 22:48:31.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nodev/loop/009.out.bad 2026-07-09 09:47:52.182882083 +0000
@@ -1,3 +1,2 @@
Running loop/009
-KERNEL add /devices/virtual/block/loop_/loop_p1 (block)
Test complete
...
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260715/202607150754.b660f5b9-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-15 6:02 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=202607150754.b660f5b9-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=daan@amutable.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox