From: Christoph Hellwig <hch@lst.de>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>
Cc: Christoph Hellwig <hch@lst.de>,
linux-scsi <linux-scsi@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [REGRESSION v4.3] scsi_dh: use-after-free when removing scsi device
Date: Sun, 4 Oct 2015 09:42:35 +0200 [thread overview]
Message-ID: <20151004074235.GA13912@lst.de> (raw)
In-Reply-To: <20151001114021.GA15125@xzibit.linux.bs1.fc.nec.co.jp>
On Thu, Oct 01, 2015 at 11:40:23AM +0000, Junichi Nomura wrote:
> On 10/01/15 14:21, Christoph Hellwig wrote:
> > Any chance you could share all your multipath tests in a git repository
> > somewhere? It seems like you're the only one actually having a good
> > set of reproducable but minimalistic tests.
>
> Hmm, sorry I don't have a public git repository...
>
> I'm using a pair of KVM guest, one for iSCSI target and the other
> for testing.
Any chance you could share your various scripts in some way to that
people doing multipath changes can run them to verify those changes?
>
> I could reproduce the crash using this loop, within a few minutes:
>
> service multipathd start
> while true; do
> multipath -F
> iscsiadm -m node --logout
> iscsiadm -m node --login
> done
>
> It might implicitly depend on udev to do some small amount of I/O
> after device uevent though.
I can't reproduce this unfortunately. I suspect udev doesn't do enough
stupid things on my old Debian test system.
next prev parent reply other threads:[~2015-10-04 7:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 0:35 [REGRESSION v4.3] scsi_dh: use-after-free when removing scsi device Junichi Nomura
2015-09-30 9:28 ` Hannes Reinecke
2015-09-30 10:35 ` Boaz Harrosh
2015-09-30 14:49 ` Hannes Reinecke
2015-09-30 15:18 ` Christoph Hellwig
2015-10-01 0:56 ` Junichi Nomura
2015-10-01 4:38 ` Junichi Nomura
2015-10-01 5:21 ` Christoph Hellwig
2015-10-01 11:40 ` Junichi Nomura
2015-10-04 7:42 ` Christoph Hellwig [this message]
2015-10-07 5:55 ` Junichi Nomura
2015-10-04 7:43 ` Christoph Hellwig
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=20151004074235.GA13912@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-scsi@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).