From: kernel test robot <oliver.sang@intel.com>
To: Li Chen <chenl311@chinatelecom.cn>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
Chaitanya Kulkarni <kch@nvidia.com>,
"Bart Van Assche" <bvanassche@acm.org>,
<linux-block@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [block] 3179a5f7f8: blktests.loop/010.fail
Date: Wed, 10 Jun 2026 10:57:44 +0800 [thread overview]
Message-ID: <202606100416.99599c18-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "blktests.loop/010.fail" on:
commit: 3179a5f7f86bcc3acd5d6fb2a29f891ef5615852 ("block: rate-limit capacity change info log")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master c10130c234c81f4a7a143edbf413080235f8d8ce]
[test failed on linux-next/master 6e845bcb78c95af935094040bd4edc3c2b6dd784]
in testcase: blktests
version: blktests-x86_64-9131687-1_20260529
with following parameters:
test: loop-010
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/202606100416.99599c18-lkp@intel.com
2026-06-05 21:40:15 echo loop/010
2026-06-05 21:40:15 ./check loop/010
loop/010 (check stale loop partition)
loop/010 (check stale loop partition) [failed]
runtime ... 92.093s
something found in dmesg:
[ 59.348633] [ T1202] run blktests loop/010 at 2026-06-05 21:40:15
[ 59.382173] [ T1223] loop0: detected capacity change from 0 to 2097152
[ 59.382922] [ T1005] loop0:
[ 59.385325] [ T1223] loop0:
[ 59.417927] [ T274] loop0: p1
[ 59.793846] [ T1267] loop0: detected capacity change from 0 to 2097152
[ 59.794835] [ T1268] loop0: p1
[ 59.796265] [ T1267] loop0: p1
[ 59.802753] [ T1272] loop0: detected capacity change from 0 to 2097152
[ 59.803800] [ T1272] loop0: p1
...
(See '/lkp/benchmarks/blktests/results/nodev/loop/010.dmesg' for the entire message)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20260610/202606100416.99599c18-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-10 2:58 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=202606100416.99599c18-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=chenl311@chinatelecom.cn \
--cc=kch@nvidia.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 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.