From: Bart Van Assche <bvanassche@acm.org>
To: Laurence Oberman <loberman@redhat.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@fb.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Panic when rebooting target server testing srp on 5.0.0-rc2
Date: Wed, 03 Apr 2019 08:09:36 -0700 [thread overview]
Message-ID: <1554304176.118779.178.camel@acm.org> (raw)
In-Reply-To: <3a0e6f4b35742a31dc5f11fab30dbdacf673b9ba.camel@redhat.com>
On Wed, 2019-04-03 at 10:53 -0400, Laurence Oberman wrote:
> Update on this issue
>
> If I reset the SRP target server and do not reboot it I do not see the
> block-mq race with the SRP initiator.
> Just resetting the SRP target array and not runing the reboot avoids
> the shutdown scripts of ib_srpt and seems somehow to prevent the race
> with the initiator code.
>
> Given that I see very little churn and activity with LIO lately I dont
> know if its worth spending more time on trying to isolate this.
>
> If anybody has an SRP native array (like DDN) and can reboot it with
> 5.x plus, that would be a good test.
>
> I will reach out to DDN and ask if they can test it.
Hi Laurence,
If the initiator side crashes it means there is a bug in the kernel at the
initiator side. It's not clear to me why you are commenting on the target
side in this e-mail thread?
Thanks,
Bart.
next prev parent reply other threads:[~2019-04-03 15:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6e19971d315f4a3ce2cc20a1c6693f4a263a280c.camel@redhat.com>
[not found] ` <7858e19ce3fc3ebf7845494a2209c58cd9e3086d.camel@redhat.com>
[not found] ` <1553113730.65329.60.camel@acm.org>
[not found] ` <3645c45e88523d4b242333d96adbb492ab100f97.camel@redhat.com>
[not found] ` <d9febee1de759206bbf4d66f6570415ae64e4f33.camel@redhat.com>
2019-03-26 15:16 ` Panic when rebooting target server testing srp on 5.0.0-rc2 Laurence Oberman
2019-03-26 19:06 ` Laurence Oberman
2019-04-03 14:53 ` Laurence Oberman
2019-04-03 15:09 ` Bart Van Assche [this message]
2019-04-03 17:58 ` Laurence Oberman
2019-03-27 1:40 ` Ming Lei
2019-03-27 12:35 ` Laurence Oberman
2019-03-27 12:56 ` Laurence Oberman
2019-03-27 22:00 ` Laurence Oberman
2019-03-27 23:34 ` Laurence Oberman
2019-03-28 1:31 ` Ming Lei
2019-03-28 14:58 ` Laurence Oberman
2019-03-28 15:09 ` Laurence Oberman
2019-04-03 17:52 ` Bart Van Assche
2019-04-03 17:59 ` Laurence Oberman
2019-04-03 18:43 ` Laurence Oberman
2019-04-03 21:47 ` Sagi Grimberg
2019-04-03 21:54 ` Bart Van Assche
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=1554304176.118779.178.camel@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@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 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).