From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
"kbusch@kernel.org" <kbusch@kernel.org>
Subject: Re: [linux-nvme:nvme-6.12] BUILD SUCCESS f54f0d0e2b1f74de85ff02013fa4886e4154aca5
Date: Thu, 24 Oct 2024 18:48:22 +0000 [thread overview]
Message-ID: <6cd3e7de-d748-4aa7-b81c-7da86be89370@nvidia.com> (raw)
In-Reply-To: <202410231604.JiCS2EBv-lkp@intel.com>
On 10/23/24 01:57, kernel test robot wrote:
> tree/branch: git://git.infradead.org/nvme.git nvme-6.12
> branch HEAD: f54f0d0e2b1f74de85ff02013fa4886e4154aca5 nvme: enhance cns version checking
>
> elapsed time: 895m
>
> configs tested: 141
> configs skipped: 2
>
nvme/012 is failing with :-
[ 1055.967692] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
HEAD:-
nvme (nvme-6.12) # git log -1
commit 3c7142f666662f77e0c91381f6b6a4fdb69ef1e5 (HEAD -> nvme-6.12,
origin/nvme-6.12)
Author: Keith Busch <kbusch@kernel.org>
Date: Wed Oct 23 08:40:26 2024 -0700
nvme: module parameter to disable pi with offsets
blktests :-
nvme/012 (tr=tcp bd=file) (run mkfs and data verification fio) [failed]
runtime 73.661s ... 96.901s
something found in dmesg:
[ 989.640076] run blktests nvme/012 at 2024-10-24 11:38:35
[ 989.688042] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
[ 989.699327] nvmet_tcp: enabling port 0 (127.0.0.1:4420)
[ 989.722715] nvmet: creating nvm controller 1 for subsystem
blktests-subsystem-1 for NQN
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
[ 989.726499] nvme nvme1: creating 48 I/O queues.
[ 989.737816] nvme nvme1: mapped 48/0/0 default/read/poll queues.
[ 989.752033] nvme nvme1: new ctrl: NQN "blktests-subsystem-1",
addr 127.0.0.1:4420, hostnqn:
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
[ 990.787401] XFS (nvme1n1): Mounting V5 Filesystem
98810ad8-32bf-43ed-8cb7-b20dfcb54c0b
[ 990.806135] XFS (nvme1n1): Ending clean mount
* [ 1055.967692] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!*
...
(See '/root/blktests/results/nodev_tr_tcp_bd_file/nvme/012.dmesg'
for the entire message)
/root/blktests/results/nodev_tr_tcp_bd_file/nvme/012.dmesg :-
[ 989.640076] run blktests nvme/012 at 2024-10-24 11:38:35
[ 989.688042] nvmet: adding nsid 1 to subsystem blktests-subsystem-1
[ 989.699327] nvmet_tcp: enabling port 0 (127.0.0.1:4420)
[ 989.722715] nvmet: creating nvm controller 1 for subsystem
blktests-subsystem-1 for NQN
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
[ 989.726499] nvme nvme1: creating 48 I/O queues.
[ 989.737816] nvme nvme1: mapped 48/0/0 default/read/poll queues.
[ 989.752033] nvme nvme1: new ctrl: NQN "blktests-subsystem-1", addr
127.0.0.1:4420, hostnqn:
nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
[ 990.787401] XFS (nvme1n1): Mounting V5 Filesystem
98810ad8-32bf-43ed-8cb7-b20dfcb54c0b
[ 990.806135] XFS (nvme1n1): Ending clean mount
[ 1055.967692] BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
[ 1055.968500] turning off the locking correctness validator.
[ 1055.969207] CPU: 13 UID: 0 PID: 11926 Comm: kworker/u192:92 Tainted:
G O N 6.12.0-rc1nvme+ #96
[ 1055.970604] Tainted: [O]=OOT_MODULE, [N]=TEST
[ 1055.971329] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014
[ 1055.976148] Workqueue: nvmet-wq nvmet_file_flush_work [nvmet]
[ 1055.978467] Call Trace:
[ 1055.979469] <TASK>
[ 1055.980381] dump_stack_lvl+0x79/0xb0
[ 1055.981248] __lock_acquire+0x1c32/0x21f0
[ 1055.982095] ? filemap_get_entry+0xf3/0x1f0
[ 1055.983081] lock_acquire+0xc9/0x2e0
[ 1055.983946] ? alloc_extent_buffer+0x268/0x900
[ 1055.984970] _raw_spin_lock+0x30/0x40
[ 1055.985902] ? alloc_extent_buffer+0x268/0x900
[ 1055.986971] alloc_extent_buffer+0x268/0x900
[ 1055.988097] btrfs_alloc_tree_block+0x12a/0x610
[ 1055.989193] ? lockdep_unlock+0x51/0xc0
[ 1055.990132] ? __lock_acquire+0x1234/0x21f0
[ 1055.991139] btrfs_force_cow_block+0x122/0x8e0
[ 1055.992182] btrfs_cow_block+0xce/0x2e0
[ 1055.993017] btrfs_search_slot+0x6fb/0xbc0
[ 1055.993895] update_block_group_item+0xae/0x1b0
[ 1055.994891] btrfs_write_dirty_block_groups+0x1ae/0x420
[ 1055.996025] ? do_raw_spin_unlock+0x4e/0xc0
[ 1055.996888] ? _raw_spin_unlock+0x23/0x40
[ 1055.997753] commit_cowonly_roots+0x1e6/0x250
[ 1055.998711] btrfs_commit_transaction+0xad1/0x1320
[ 1055.999747] btrfs_sync_file+0x471/0x610
[ 1056.000620] nvmet_file_flush_work+0x26/0x40 [nvmet]
[ 1056.001764] process_one_work+0x1f9/0x630
[ 1056.002599] worker_thread+0x191/0x330
[ 1056.003435] ? __pfx_worker_thread+0x10/0x10
[ 1056.004399] kthread+0xe1/0x120
[ 1056.005102] ? __pfx_kthread+0x10/0x10
[ 1056.005923] ret_from_fork+0x31/0x50
[ 1056.006684] ? __pfx_kthread+0x10/0x10
[ 1056.007528] ret_from_fork_asm+0x1a/0x30
[ 1056.008391] </TASK>
[ 1086.403029] XFS (nvme1n1): Unmounting Filesystem
98810ad8-32bf-43ed-8cb7-b20dfcb54c0b
[ 1086.433707] nvme nvme1: Removing ctrl: NQN "blktests-subsystem-1"
[ 1087.079755] Key type psk unregistered
I've not seen this lock dep message ever if it's a false positive please
ignore.
-ck
prev parent reply other threads:[~2024-10-24 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 8:57 [linux-nvme:nvme-6.12] BUILD SUCCESS f54f0d0e2b1f74de85ff02013fa4886e4154aca5 kernel test robot
2024-10-24 18:48 ` Chaitanya Kulkarni [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=6cd3e7de-d748-4aa7-b81c-7da86be89370@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox