linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: David Dillow <dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org>
Cc: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Vu Pham <vu-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Alex Turin <alextu-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH v2 2/2] IB/srp: Avoid endless SCSI error handling loop
Date: Fri, 14 Dec 2012 17:30:42 +0100	[thread overview]
Message-ID: <50CB5432.8040204@acm.org> (raw)
In-Reply-To: <1355501996.18309.16.camel-zHLflQxYYDO4Hhoo1DtQwJ9G+ZOsUmrO@public.gmane.org>

On 12/14/12 17:19, David Dillow wrote:
> On Fri, 2012-12-14 at 17:12 +0100, Bart Van Assche wrote:
>> On 12/14/12 16:55, David Dillow wrote:
>>> This is much more than your original patch that Alex claimed fixed his
>>> issues; are you not merging two separate issues?
>>   >
>>> Also, there's no reason to invoke srp_send_tsk_mgmt() if we're not
>>> connected or the QP is in error -- for those cases, it makes sense to
>>> just abort the command directly. Similarly, we should probably be
>>> checking the status of srp_send_tsk_mgmt() and failing -- or checking
>>> qp_in_error/connected again and directly aborting if we have problems.
>>
>> Thanks for the quick reply. You might have missed Vu's message though.
>> Vu Pham reported that v1 of this patch did not fix the endless error
>> handling loop (see e.g.
>> http://www.mail-archive.com/linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg13713.html).
>
> I saw that, but I also saw your message asking if he was sure he was
> running with your patch, and I never saw a public reply to clarify.
>
> I saw a message from him yesterday that running your fixes branch did
> work, but with no posting of updated patches I assumed that was v1 still
> -- was he testing v2?

Hello Dave,

There has been some off-list communication too in which Vu explained me 
that v1 was not sufficient but that v2 did help.

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

  parent reply	other threads:[~2012-12-14 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-14 15:32 [PATCH v2] IB/SRP patches for kernel 3.8 Bart Van Assche
     [not found] ` <50CB46A4.4050300-HInyCGIudOg@public.gmane.org>
2012-12-14 15:34   ` [PATCH v2 1/2] IB/srp: Track connection state properly Bart Van Assche
     [not found]     ` <50CB4713.4080909-HInyCGIudOg@public.gmane.org>
2012-12-14 15:48       ` David Dillow
2012-12-14 15:38   ` [PATCH v2 2/2] IB/srp: Avoid endless SCSI error handling loop Bart Van Assche
     [not found]     ` <50CB47E7.2060308-HInyCGIudOg@public.gmane.org>
2012-12-14 15:55       ` David Dillow
     [not found]         ` <1355500552.18309.11.camel-zHLflQxYYDO4Hhoo1DtQwJ9G+ZOsUmrO@public.gmane.org>
2012-12-14 16:12           ` Bart Van Assche
     [not found]             ` <50CB4FEB.3080104-HInyCGIudOg@public.gmane.org>
2012-12-14 16:19               ` David Dillow
     [not found]                 ` <1355501996.18309.16.camel-zHLflQxYYDO4Hhoo1DtQwJ9G+ZOsUmrO@public.gmane.org>
2012-12-14 16:30                   ` Bart Van Assche [this message]
     [not found]                     ` <50CB5432.8040204-HInyCGIudOg@public.gmane.org>
2012-12-14 18:14                       ` Vu Pham
2012-12-19  4:09               ` David Dillow
     [not found]                 ` <1355890164.23969.0.camel-1q1vX8mYZiGLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2012-12-19 14:15                   ` 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=50CB5432.8040204@acm.org \
    --to=bvanassche-hinycgiudog@public.gmane.org \
    --cc=alextu-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=dave-i1Mk8JYDVaaSihdK6806/g@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org \
    --cc=vu-VPRAkNaXOzVWk0Htik3J/w@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 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).