From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: dan carpenter <d_carpenter@sbcglobal.net>
Cc: Zwane Mwaikambo <zwane@holomorphy.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
wrlk@riede.org
Subject: Re: Any hope for ide-scsi (error handling)?
Date: 16 Mar 2003 01:05:51 +0000 [thread overview]
Message-ID: <1047776751.1330.9.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <200303152012.h2FKCulK283698@pimout2-ext.prodigy.net>
On Sat, 2003-03-15 at 02:52, dan carpenter wrote:
> > > Here is at least one bad call to schedule() in
> > > static int idescsi_reset (Scsi_Cmnd *cmd)
> >
> > Apart from the schedule with the ide_lock held, what is that code actually
> > doing?
> >
> > Zwane
>
> Hm... Good question. I have no idea what the while loop is for.
See 2.4.21-pre5-ac2 or later. You are discussing obsolete and known
broken code otherwise. The -ac code is closer to working and has most
but alas it seems not all the reset stuff fixed. While this works for
2.4 the 2.5 ide-scsi error handling has been rewritten by someone for
the scsi changes and so differs from both the 2.4 style scsi error
handling and reality by some margin. Once the reset code settles down
in 2.4.21-pre5-ac and 2.5.64-ac I'll take a crack at ide-scsi again.
prev parent reply other threads:[~2003-03-15 23:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 18:55 Zwane Mwaikambo
2003-03-15 2:05 ` dan carpenter
2003-03-15 19:53 ` Zwane Mwaikambo
2003-03-15 2:52 ` dan carpenter
2003-03-15 20:23 ` Zwane Mwaikambo
2003-03-15 21:01 ` Willem Riede
2003-03-15 4:43 ` dan carpenter
2003-03-15 21:11 ` Zwane Mwaikambo
2003-03-15 22:29 ` Willem Riede
2003-03-16 1:23 ` Alan Cox
2003-03-16 0:55 ` Willem Riede
2003-03-16 21:41 ` Alan Cox
2003-03-15 20:25 ` bert hubert
2003-03-15 20:41 ` Zwane Mwaikambo
2003-03-15 20:55 ` Zwane Mwaikambo
2003-03-16 1:05 ` Alan Cox [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=1047776751.1330.9.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=d_carpenter@sbcglobal.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wrlk@riede.org \
--cc=zwane@holomorphy.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
all inboxes | Powered by JetHome®