From: snitzer@redhat.com (Mike Snitzer)
Subject: 'modprobe nvme_core multipath=N' crashes in face of multipath fabric
Date: Tue, 10 Apr 2018 16:49:53 -0400 [thread overview]
Message-ID: <20180410204953.GA17979@redhat.com> (raw)
This isn't new since the 4.17 merge or anything, I first noticed this
issue existed while using a 4.16-rc4 kernel.
modprobe nvme_core multipath=N
Using mptest's nvme_4port_create.sh
git clone git://github.com/snitm/mptest.git
cd mptest/lib/unittests
perl -pi -e 's|/dev/pmem0|/dev/some_test_device|' nvme_4port_create.sh
./nvme_4port_create.sh
[ 2309.845915] nvmet: adding nsid 1 to subsystem mptestnqn
[ 2310.019820] nvmet: creating controller 1 for subsystem mptestnqn for NQN nqn.2014-08.org.nvmexpress:uuid:71a69a69-edb9-4d51-8cbf-1c29778534ab.
[ 2310.034201] nvme nvme1: NVME-FC{0}: new ctrl: NQN "mptestnqn"
[ 2310.041705] nvmet: creating controller 2 for subsystem mptestnqn for NQN nqn.2014-08.org.nvmexpress:uuid:71a69a69-edb9-4d51-8cbf-1c29778534ab.
[ 2310.056005] nvme nvme2: NVME-FC{1}: new ctrl: NQN "mptestnqn"
[ 2310.056314] sysfs: cannot create duplicate filename '/class/block/nvme1n1'
[ 2310.063386] nvmet: creating controller 3 for subsystem mptestnqn for NQN nqn.2014-08.org.nvmexpress:uuid:71a69a69-edb9-4d51-8cbf-1c29778534ab.
[ 2310.068637] CPU: 3 PID: 1791 Comm: kworker/u497:1 Not tainted 4.16.0.snitm+ #13
[ 2310.088705] Hardware name: Supermicro SYS-1029P-WTR/X11DDW-L, BIOS 2.0a 12/06/2017
[ 2310.096274] Workqueue: nvme-wq nvme_scan_work [nvme_core]
[ 2310.101669] Call Trace:
[ 2310.104129] dump_stack+0x5a/0x73
[ 2310.107444] sysfs_warn_dup+0x58/0x70
[ 2310.111109] sysfs_do_create_link_sd.isra.2+0xa3/0xb0
[ 2310.116162] device_add+0x2ac/0x5f0
[ 2310.119658] __device_add_disk+0x19c/0x4a0
[ 2310.123754] nvme_validate_ns+0x4d2/0x860 [nvme_core]
[ 2310.128807] ? wake_up_q+0x70/0x70
[ 2310.132214] nvme_scan_work+0x211/0x2d0 [nvme_core]
[ 2310.137095] process_one_work+0x158/0x360
[ 2310.141103] worker_thread+0x47/0x3e0
[ 2310.144772] kthread+0xf8/0x130
[ 2310.147917] ? max_active_store+0x80/0x80
[ 2310.151929] ? kthread_bind+0x10/0x10
[ 2310.155595] ? do_syscall_64+0x74/0x1a0
[ 2310.159435] ? SyS_exit_group+0x10/0x10
[ 2310.163273] ret_from_fork+0x35/0x40
[ 2310.166872] nvme nvme3: NVME-FC{2}: new ctrl: NQN "mptestnqn"
[ 2310.166875] ------------[ cut here ]------------
[ 2310.167189] sysfs: cannot create duplicate filename '/class/block/nvme1n1'
[ 2310.167190] CPU: 3 PID: 8111 Comm: kworker/u497:3 Not tainted 4.16.0.snitm+ #13
[ 2310.167191] Hardware name: Supermicro SYS-1029P-WTR/X11DDW-L, BIOS 2.0a 12/06/2017
[ 2310.167194] Workqueue: nvme-wq nvme_scan_work [nvme_core]
[ 2310.167194] Call Trace:
[ 2310.167196] dump_stack+0x5a/0x73
[ 2310.167198] sysfs_warn_dup+0x58/0x70
[ 2310.167199] sysfs_do_create_link_sd.isra.2+0xa3/0xb0
[ 2310.167200] device_add+0x2ac/0x5f0
[ 2310.167202] __device_add_disk+0x19c/0x4a0
[ 2310.167205] nvme_validate_ns+0x4d2/0x860 [nvme_core]
[ 2310.167206] ? wake_up_q+0x70/0x70
[ 2310.167208] nvme_scan_work+0x211/0x2d0 [nvme_core]
[ 2310.167210] process_one_work+0x158/0x360
[ 2310.167211] worker_thread+0x47/0x3e0
[ 2310.167212] kthread+0xf8/0x130
[ 2310.167213] ? max_active_store+0x80/0x80
[ 2310.167214] ? kthread_bind+0x10/0x10
[ 2310.167215] ret_from_fork+0x35/0x40
[ 2310.167225] ------------[ cut here ]------------
[ 2310.167226] kernel BUG at fs/sysfs/group.c:111!
next reply other threads:[~2018-04-10 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 20:49 Mike Snitzer [this message]
2018-04-11 13:45 ` 'modprobe nvme_core multipath=N' crashes in face of multipath fabric Keith Busch
2018-04-11 14:17 ` Mike Snitzer
2018-04-11 17:58 ` Keith Busch
2018-04-11 21:46 ` Mike Snitzer
2018-04-12 8:12 ` Sagi Grimberg
2018-04-12 22:28 ` Keith Busch
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=20180410204953.GA17979@redhat.com \
--to=snitzer@redhat.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 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.