From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-scsi <linux-scsi@vger.kernel.org>
Cc: Mike Anderson <andmike@linux.vnet.ibm.com>,
Jens Axboe <Jens.Axboe@oracle.com>
Subject: [PATCH 0/7] fix block timeout residue problems
Date: Sun, 30 Nov 2008 10:12:25 -0600 [thread overview]
Message-ID: <1228061545.4115.10.camel@localhost.localdomain> (raw)
It looks like there was only a partial conversion of the SCSI layer to
the block timeout. The missing piece was killing timeout in struct
scsi_device and leaving it with a zero value. This has already resulted
in a regression:
http://bugzilla.kernel.org/show_bug.cgi?id=12120
But on closer inspection, there were lots of other dangling driver uses
of the timeout value which would likewise have introduced hard to trace
regressions.
This patch series eliminates the timeout variable from struct
scsi_device and makes everything uniformly use the block timeout. Any
wrong use of the scsi device timeout will now result in a compile
failure.
It's getting late in the -rc series to push this through, but hopefully
it won't delay 2.6.28 too much.
James
reply other threads:[~2008-11-30 16:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1228061545.4115.10.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Jens.Axboe@oracle.com \
--cc=andmike@linux.vnet.ibm.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