From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Dongsu Park <dongsu.park-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sebastian Riemer
<sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>,
David Dillow <dillowda-1Heg1YXhbW8@public.gmane.org>
Subject: Re: [PATCH] IB/srp: disconnect to SRP target before removing SCSI host
Date: Fri, 11 Jan 2013 20:42:07 +0100 [thread overview]
Message-ID: <50F06B0F.9090800@acm.org> (raw)
In-Reply-To: <20130111140706.GK7859-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 01/11/13 15:07, Dongsu Park wrote:
> However, that action will hang forever until the target machine comes up
> again. Precisely it's blocked on scsi_execute() directly after sending
> SYNCHRONIZE_CACHE command to the first target of the host. As IB stack
> is not able to give any response, further target remove cannot be done.
This is the part that needs further research. If a SCSI command is not
yet finished after the SCSI timeout expired the SCSI error handler will
try to abort the command. scsi_execute() should finish in time. If not,
something is wrong either in the LLD (ib_srp), the SCSI core or in the
block layer. It would help to know what exactly was going on.
Bart.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-01-11 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 13:56 [PATCH] IB/srp: disconnect to SRP target before removing SCSI host Dongsu Park
[not found] ` <1357394162-26316-1-git-send-email-dongsu.park-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2013-01-07 11:34 ` Bart Van Assche
[not found] ` <50EAB2E1.7050702-HInyCGIudOg@public.gmane.org>
2013-01-07 18:17 ` David Dillow
2013-01-11 14:07 ` Dongsu Park
[not found] ` <20130111140706.GK7859-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-11 19:42 ` 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=50F06B0F.9090800@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=dillowda-1Heg1YXhbW8@public.gmane.org \
--cc=dongsu.park-EIkl63zCoXaH+58JC4qpiA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sebastian.riemer-EIkl63zCoXaH+58JC4qpiA@public.gmane.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 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.