From: Bart Van Assche <bvanassche@acm.org>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: James Bottomley <jbottomley@odin.com>,
Hannes Reinecke <hare@suse.de>, Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: Fix a bdi reregistration race
Date: Sun, 20 Sep 2015 06:49:27 -0700 [thread overview]
Message-ID: <55FEB967.7040500@acm.org> (raw)
In-Reply-To: <55FE8324.9000604@dev.mellanox.co.il>
On 09/20/15 02:57, Sagi Grimberg wrote:
> On 9/19/2015 3:23 AM, Bart Van Assche wrote:
>> Unregister and reregister BDI devices in the proper order. This patch
>> avoids that the following kernel warning can get triggered:
>
> Can you share the scenario that reproduced this? I think I might
> have seen this before.
Hello Sagi,
The details of the setup on which I can reproduce the reported behavior
easily are as follows:
* Several kernel debugging options were enabled on the initiator system
(PROVE_LOCKING, SLUB_DEBUG, KMEMLEAK, ...).
* srp_daemon and multipathd were running on the initiator system.
* Four IB ports were present the initiator system.
* Eight IB ports were present the target system.
* 100 LUNs were defined on the target system.
* As a result, 3200 /dev/sd* device nodes were created on the
initiator system by the SRP initiator driver.
* The following command was run on the initiator system:
for p in /sys/class/srp_remote_ports/*; do echo 1 >$p/delete & done;
wait; dmsetup remove_all
Bart.
prev parent reply other threads:[~2015-09-20 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 0:23 [PATCH] scsi: Fix a bdi reregistration race Bart Van Assche
2015-09-19 7:46 ` Hannes Reinecke
2015-09-20 9:57 ` Sagi Grimberg
2015-09-20 13:49 ` Bart Van Assche [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=55FEB967.7040500@acm.org \
--to=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jbottomley@odin.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sagig@dev.mellanox.co.il \
/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.