From: kernel test robot <oliver.sang@intel.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Christoph Hellwig <hch@lst.de>, <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, <linux-nvme@lists.infradead.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, Wen Xiong <wenxiong@linux.ibm.com>,
Keith Busch <kbusch@kernel.org>, Ming Lei <ming.lei@redhat.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH V3 14/14] blk-mq: add helpers for treating kdump kernel
Date: Thu, 10 Aug 2023 16:00:39 +0800 [thread overview]
Message-ID: <202308101503.67a2d533-oliver.sang@intel.com> (raw)
In-Reply-To: <20230808104239.146085-15-ming.lei@redhat.com>
Hello,
kernel test robot noticed "WARNING:at_drivers/block/null_blk/main.c:#null_map_queues" on:
commit: 8ec7debf0b62ddf5f62e18b886925462215ab98b ("[PATCH V3 14/14] blk-mq: add helpers for treating kdump kernel")
url: https://github.com/intel-lab-lkp/linux/commits/Ming-Lei/blk-mq-add-blk_mq_max_nr_hw_queues/20230809-003555
base: https://git.kernel.org/cgit/linux/kernel/git/mkp/scsi.git for-next
patch link: https://lore.kernel.org/all/20230808104239.146085-15-ming.lei@redhat.com/
patch subject: [PATCH V3 14/14] blk-mq: add helpers for treating kdump kernel
in testcase: boot
compiler: gcc-12
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
(please refer to attached dmesg/kmsg for entire log/backtrace)
+-----------------------------------------------------------+------------+------------+
| | 27da637b41 | 8ec7debf0b |
+-----------------------------------------------------------+------------+------------+
| boot_successes | 12 | 0 |
| boot_failures | 0 | 12 |
| WARNING:at_drivers/block/null_blk/main.c:#null_map_queues | 0 | 12 |
| EIP:null_map_queues | 0 | 12 |
| BUG:kernel_NULL_pointer_dereference,address | 0 | 12 |
| Oops:#[##] | 0 | 12 |
| EIP:group_cpus_evenly | 0 | 12 |
| Kernel_panic-not_syncing:Fatal_exception | 0 | 12 |
+-----------------------------------------------------------+------------+------------+
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/202308101503.67a2d533-oliver.sang@intel.com
[ 7.742766][ T1] null_blk: tag set has unexpected nr_hw_queues: 1
[ 7.744704][ T1] ------------[ cut here ]------------
[ 7.745825][ T1] WARNING: CPU: 0 PID: 1 at drivers/block/null_blk/main.c:1615 null_map_queues+0x56/0xdb
[ 7.748029][ T1] Modules linked in:
[ 7.748923][ T1] CPU: 0 PID: 1 Comm: swapper Tainted: G T 6.5.0-rc1-00100-g8ec7debf0b62 #10 05d847e43b9b6f584ad59352c89de6920a7d94da
[ 7.751662][ T1] EIP: null_map_queues+0x56/0xdb
[ 7.753366][ T1] Code: b0 b4 01 00 00 8d 0c 37 39 ca 74 29 8b b8 b0 01 00 00 8b b0 b8 01 00 00 8d 04 37 39 c2 74 16 52 68 6d 34 9b 42 e8 f8 89 84 ff <0f> 0b 31
f6 5a bf 01 00 00 00 59 8d 43 04 31 c9 31 d2 89 45 f0 3b
[ 7.757272][ T1] EAX: 00000030 EBX: 46131e1c ECX: 00000000 EDX: 00000000
[ 7.758794][ T1] ESI: 00000001 EDI: 00000001 EBP: 40343e88 ESP: 40343e68
[ 7.760257][ T1] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010246
[ 7.761810][ T1] CR0: 80050033 CR2: ffd99000 CR3: 0343e000 CR4: 000406d0
[ 7.763254][ T1] Call Trace:
[ 7.763953][ T1] ? show_regs+0x60/0x70
[ 7.764872][ T1] ? null_map_queues+0x56/0xdb
[ 7.765908][ T1] ? __warn+0x8c/0x10a
[ 7.766754][ T1] ? report_bug+0xdd/0x13e
[ 7.767719][ T1] ? null_map_queues+0x56/0xdb
[ 7.768721][ T1] ? exc_overflow+0x41/0x41
[ 7.769668][ T1] ? handle_bug+0x2b/0x53
[ 7.770532][ T1] ? exc_invalid_op+0x24/0x6a
[ 7.771501][ T1] ? handle_exception+0x11d/0x11d
[ 7.772572][ T1] ? lockdep_next_lockchain+0x18/0x2b
[ 7.773697][ T1] ? exc_overflow+0x41/0x41
[ 7.774604][ T1] ? null_map_queues+0x56/0xdb
[ 7.775593][ T1] ? exc_overflow+0x41/0x41
[ 7.776561][ T1] ? null_map_queues+0x56/0xdb
[ 7.777534][ T1] ? kmalloc_array_node+0x19/0x28
[ 7.778828][ T1] ? blk_mq_update_queue_map+0x57/0x7e
[ 7.779975][ T1] ? blk_mq_alloc_tag_set+0x1eb/0x353
[ 7.781115][ T1] ? null_init_tag_set+0xd7/0xe6
[ 7.782155][ T1] ? null_add_dev+0x1d9/0x5ef
[ 7.783128][ T1] ? null_alloc_dev+0x7a/0x1c2
[ 7.784144][ T1] ? null_init+0x26d/0x36b
[ 7.785126][ T1] ? do_one_initcall+0x77/0x1b9
[ 7.786097][ T1] ? virtio_blk_init+0xbf/0xbf
[ 7.787076][ T1] ? do_initcalls+0x176/0x1ba
[ 7.788080][ T1] ? kernel_init_freeable+0xe9/0x13c
[ 7.792635][ T1] ? rest_init+0x11d/0x11d
[ 7.793557][ T1] ? kernel_init+0x12/0xf7
[ 7.794469][ T1] ? ret_from_fork+0x1c/0x30
[ 7.795465][ T1] irq event stamp: 321017
[ 7.796352][ T1] hardirqs last enabled at (321027): [<41095389>] __up_console_sem+0x59/0x71
[ 7.798190][ T1] hardirqs last disabled at (321036): [<41095370>] __up_console_sem+0x40/0x71
[ 7.800028][ T1] softirqs last enabled at (320984): [<41f25ca9>] __do_softirq+0x279/0x2b7
[ 7.801854][ T1] softirqs last disabled at (320975): [<4101cf25>] call_on_stack+0x40/0x50
[ 7.803562][ T1] ---[ end trace 0000000000000000 ]---
[ 7.804950][ T1] BUG: kernel NULL pointer dereference, address: 00000010
[ 7.805688][ T1] #PF: supervisor write access in kernel mode
[ 7.805688][ T1] #PF: error_code(0x0002) - not-present page
[ 7.805688][ T1] *pde = 00000000
[ 7.805688][ T1] Oops: 0002 [#1] PREEMPT
[ 7.805688][ T1] CPU: 0 PID: 1 Comm: swapper Tainted: G W T 6.5.0-rc1-00100-g8ec7debf0b62 #10 05d847e43b9b6f584ad59352c89de6920a7d94da
[ 7.805688][ T1] EIP: group_cpus_evenly+0x24/0x2e
[ 7.805688][ T1] Code: c9 e9 a1 91 8d 00 55 89 e5 ba 04 00 00 00 f7 e2 70 0e ba c0 0d 00 00 e8 2e 87 b4 ff 85 c0 75 04 31 c0 eb 08 8b 15 a8 1b 34 43 <89> 10 5d
31 d2 e9 73 91 8d 00 55 89 e5 56 53 8b 1d 84 5f 32 43 85
[ 7.805688][ T1] EAX: 00000010 EBX: 46131e38 ECX: 00000000 EDX: 00000001
[ 7.805688][ T1] ESI: 00000000 EDI: 00000001 EBP: 40343e58 ESP: 40343e58
[ 7.805688][ T1] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010202
[ 7.805688][ T1] CR0: 80050033 CR2: 00000010 CR3: 0343e000 CR4: 000406d0
[ 7.805688][ T1] Call Trace:
[ 7.805688][ T1] ? show_regs+0x60/0x70
[ 7.805688][ T1] ? __die_body+0x13/0x52
[ 7.805688][ T1] ? __die+0x22/0x2c
[ 7.805688][ T1] ? page_fault_oops+0x4c/0x7f
[ 7.805688][ T1] ? kernelmode_fixup_or_oops+0x8b/0x9d
[ 7.805688][ T1] ? __bad_area_nosemaphore+0x40/0x16c
[ 7.805688][ T1] ? bad_area_nosemaphore+0xa/0x17
[ 7.805688][ T1] ? do_user_addr_fault+0xdd/0x396
[ 7.805688][ T1] ? trace_irq_disable+0x3b/0x4e
[ 7.805688][ T1] ? exc_page_fault+0xf6/0x120
[ 7.805688][ T1] ? pvclock_clocksource_read_nowd+0x167/0x167
[ 7.805688][ T1] ? handle_exception+0x11d/0x11d
[ 7.805688][ T1] ? pvclock_clocksource_read_nowd+0x167/0x167
[ 7.805688][ T1] ? group_cpus_evenly+0x24/0x2e
[ 7.805688][ T1] ? pvclock_clocksource_read_nowd+0x167/0x167
[ 7.805688][ T1] ? group_cpus_evenly+0x24/0x2e
[ 7.805688][ T1] ? blk_mq_map_queues+0xf/0x46
[ 7.805688][ T1] ? null_map_queues+0xbc/0xdb
[ 7.805688][ T1] ? blk_mq_update_queue_map+0x57/0x7e
[ 7.805688][ T1] ? blk_mq_alloc_tag_set+0x1eb/0x353
[ 7.805688][ T1] ? null_init_tag_set+0xd7/0xe6
[ 7.805688][ T1] ? null_add_dev+0x1d9/0x5ef
[ 7.805688][ T1] ? null_alloc_dev+0x7a/0x1c2
[ 7.805688][ T1] ? null_init+0x26d/0x36b
[ 7.805688][ T1] ? do_one_initcall+0x77/0x1b9
[ 7.805688][ T1] ? virtio_blk_init+0xbf/0xbf
[ 7.805688][ T1] ? do_initcalls+0x176/0x1ba
[ 7.805688][ T1] ? kernel_init_freeable+0xe9/0x13c
[ 7.805688][ T1] ? rest_init+0x11d/0x11d
[ 7.805688][ T1] ? kernel_init+0x12/0xf7
[ 7.805688][ T1] ? ret_from_fork+0x1c/0x30
[ 7.805688][ T1] Modules linked in:
[ 7.805688][ T1] CR2: 0000000000000010
[ 7.805688][ T1] ---[ end trace 0000000000000000 ]---
[ 7.805688][ T1] EIP: group_cpus_evenly+0x24/0x2e
[ 7.805688][ T1] Code: c9 e9 a1 91 8d 00 55 89 e5 ba 04 00 00 00 f7 e2 70 0e ba c0 0d 00 00 e8 2e 87 b4 ff 85 c0 75 04 31 c0 eb 08 8b 15 a8 1b 34 43 <89> 10 5d
31 d2 e9 73 91 8d 00 55 89 e5 56 53 8b 1d 84 5f 32 43 85
[ 7.805688][ T1] EAX: 00000010 EBX: 46131e38 ECX: 00000000 EDX: 00000001
[ 7.805688][ T1] ESI: 00000000 EDI: 00000001 EBP: 40343e58 ESP: 40343e58
[ 7.805688][ T1] DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010202
[ 7.805688][ T1] CR0: 80050033 CR2: 00000010 CR3: 0343e000 CR4: 000406d0
[ 7.805688][ T1] Kernel panic - not syncing: Fatal exception
[ 7.805688][ T1] Kernel Offset: disabled
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230810/202308101503.67a2d533-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-08-10 8:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 10:42 [PATCH V3 0/14] blk-mq: fix wrong queue mapping for kdump kernel Ming Lei
2023-08-08 10:42 ` [PATCH V3 01/14] blk-mq: add blk_mq_max_nr_hw_queues() Ming Lei
2023-08-09 13:44 ` Christoph Hellwig
2023-08-10 0:09 ` Ming Lei
2023-08-10 1:18 ` Baoquan He
2023-08-10 2:06 ` Ming Lei
2023-08-10 3:01 ` Baoquan He
2023-08-11 7:53 ` Hari Bathini
2023-09-05 5:03 ` Baoquan He
2023-08-11 13:10 ` Christoph Hellwig
2023-08-08 10:42 ` [PATCH V3 02/14] nvme-pci: use blk_mq_max_nr_hw_queues() to calculate io queues Ming Lei
2023-08-08 10:42 ` [PATCH V3 03/14] ublk: limit max allowed nr_hw_queues Ming Lei
2023-08-08 10:42 ` [PATCH V3 04/14] virtio-blk: limit max allowed submit queues Ming Lei
2023-08-10 19:23 ` Michael S. Tsirkin
2023-08-08 10:42 ` [PATCH V3 05/14] scsi: core: add helper of scsi_max_nr_hw_queues() Ming Lei
2023-08-08 10:42 ` [PATCH V3 06/14] scsi: lpfc: use blk_mq_max_nr_hw_queues() to calculate io vectors Ming Lei
2023-08-08 10:42 ` [PATCH V3 07/14] scsi: mpi3mr: take blk_mq_max_nr_hw_queues() into account for calculating " Ming Lei
2023-08-08 10:42 ` [PATCH V3 08/14] scsi: megaraid: " Ming Lei
2023-08-08 10:42 ` [PATCH V3 09/14] scsi: mpt3sas: " Ming Lei
2023-08-08 10:42 ` [PATCH V3 10/14] scsi: pm8001: " Ming Lei
2023-08-08 10:42 ` [PATCH V3 11/14] scsi: hisi: " Ming Lei
2023-08-08 10:42 ` [PATCH V3 12/14] scsi: ufs: limit max allowed nr_hw_queues Ming Lei
2023-08-08 10:42 ` [PATCH V3 13/14] scsi: storvsc: " Ming Lei
2023-08-08 10:42 ` [PATCH V3 14/14] blk-mq: add helpers for treating kdump kernel Ming Lei
2023-08-10 8:00 ` kernel test robot [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=202308101503.67a2d533-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=wenxiong@linux.ibm.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