From: Hannes Reinecke <hare@suse.de>
To: Christof Schmitt <christof.schmitt@de.ibm.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
James Smart <james.smart@emulex.com>,
James Bottomley <James.Bottomley@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Protect against overflow in dev_loss_tmo
Date: Fri, 26 Mar 2010 10:50:17 +0100 [thread overview]
Message-ID: <4BAC8359.7020106@suse.de> (raw)
In-Reply-To: <20100324160231.GA26364@schmichrtp.mainz.de.ibm.com>
Christof Schmitt wrote:
[ .. ]
>
> I just posted the complete version of the patch and the adaption of
> zfcp:
> http://marc.info/?l=linux-scsi&m=126944631211269&w=2
> http://marc.info/?l=linux-scsi&m=126944631211272&w=2
> http://marc.info/?l=linux-scsi&m=126944631611276&w=2
>
> Any comments about this approach for unblocking the scsi eh thread?
>
That looks like a really good idea. And it might even solve the problem
we had with path flapping on a multipathed raid device.
I'll give it a go here locally.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-03-26 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 9:18 [PATCH] Protect against overflow in dev_loss_tmo Hannes Reinecke
2010-03-09 14:14 ` James Smart
2010-03-16 13:04 ` Christof Schmitt
2010-03-17 9:40 ` Hannes Reinecke
2010-03-18 4:33 ` Mike Christie
2010-03-18 4:24 ` Mike Christie
2010-03-22 14:12 ` Christof Schmitt
2010-03-24 16:02 ` Christof Schmitt
2010-03-26 9:50 ` Hannes Reinecke [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=4BAC8359.7020106@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@suse.de \
--cc=christof.schmitt@de.ibm.com \
--cc=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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.