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>, Jens Axboe <axboe@kernel.dk>,
<linux-block@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [block] 30f1e72414: blktests.nvme/019.device.fail
Date: Tue, 22 Apr 2025 16:48:25 +0800 [thread overview]
Message-ID: <202504221628.32af97d8-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "blktests.nvme/019.device.fail" on:
commit: 30f1e724142242a453f92d90b33e030014900bf0 ("block: move discard checks into the ioctl handler")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 8560697b23dc2f405cb463af2b17256a9888129d]
[test failed on linux-next/master bc8aa6cdadcc00862f2b5720e5de2e17f696a081]
in testcase: blktests
version: blktests-x86_64-236edfd-1_20250318
with following parameters:
disk: 1SSD
test: nvme-group-00
nvme_trtype: rdma
config: x86_64-rhel-9.4-func
compiler: gcc-12
test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz (Ice Lake) with 256G 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/202504221628.32af97d8-lkp@intel.com
nvme/019 (tr=rdma bd=device) (test NVMe DSM Discard command)
nvme/019 (tr=rdma bd=device) (test NVMe DSM Discard command) [failed]
runtime ... 0.920s
--- tests/nvme/019.out 2025-03-18 16:49:58.000000000 +0000
+++ /mnt/nvme-group-00/nodev_tr_rdma_bd_device/nvme/019.out.bad 2024-08-25 17:37:26.300999900 +0000
@@ -1,4 +1,4 @@
Running nvme/019
-NVMe DSM: success
+NVMe status: Command Size Limit Exceeded(0x6183)
disconnected 1 controller(s)
Test complete
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250422/202504221628.32af97d8-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-22 8:48 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=202504221628.32af97d8-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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.