From: kernel test robot <oliver.sang@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Christian Brauner <brauner@kernel.org>,
Josef Bacik <josef@toxicpanda.com>, <linux-block@vger.kernel.org>,
<nbd@other.debian.org>, <oliver.sang@intel.com>
Subject: [linus:master] [nbd] 0c1c9a27ce: blktests.nbd/002.fail
Date: Tue, 12 Sep 2023 13:08:16 +0800 [thread overview]
Message-ID: <202309121232.767ff8c4-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "blktests.nbd/002.fail" on:
commit: 0c1c9a27ce909e3988f8c6407e26a22a7e1cd276 ("nbd: call blk_mark_disk_dead in nbd_clear_sock_ioctl")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 0bb80ecc33a8fb5a682236443c1e740d5c917d1d]
[test failed on linux-next/master 7bc675554773f09d88101bf1ccfc8537dc7c0be9]
in testcase: blktests
version: blktests-x86_64-2045e8d-1_20230905
with following parameters:
test: nbd-002
compiler: gcc-12
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) 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/202309121232.767ff8c4-oliver.sang@intel.com
2023-09-11 10:11:30 echo nbd/002
2023-09-11 10:11:30 ./check nbd/002
nbd/002 (tests on partition handling for an nbd device)
nbd/002 (tests on partition handling for an nbd device) [failed]
runtime ... 4.474s
--- tests/nbd/002.out 2023-09-05 16:51:33.000000000 +0000
+++ /lkp/benchmarks/blktests/results/nodev/nbd/002.out.bad 2023-09-11 10:11:35.949540198 +0000
@@ -1,4 +1,4 @@
Running nbd/002
Testing IOCTL path
Testing the netlink path
-Test complete
+Didn't have parition on the netlink path
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230912/202309121232.767ff8c4-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-12 5:08 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=202309121232.767ff8c4-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nbd@other.debian.org \
--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