From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Drew Winstel <raw@dslr.net>
Cc: linux-ide@vger.kernel.org, John Treubig <jtreubig@hotmail.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: ATA Write Error and Time-out Notification in User Space
Date: Thu, 22 Dec 2005 01:09:16 +0000 [thread overview]
Message-ID: <1135213756.10383.9.camel@localhost.localdomain> (raw)
In-Reply-To: <200512201831.38592.raw@dslr.net>
On Maw, 2005-12-20 at 18:31 -0600, Drew Winstel wrote:
> With the application that John is using (namely, it delivers reads and writes
> directly to the drive via various SG ioctls), the file system is not an
> issue, hence wanting the errors to be returned to userspace.
>
> I presume this means that John would have to look at the block level error
> handling as opposed to the SCSI level?
If you are using the sg ioctls then the commands are dispatched and the
results come through the request queues but not the block layer above.
In that case you really shouldn't be seeing a hang.
Alan
next prev parent reply other threads:[~2005-12-22 1:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 21:55 ATA Write Error and Time-out Notification in User Space John Treubig
2005-12-20 22:50 ` Alan Cox
2005-12-21 0:31 ` Drew Winstel
2005-12-22 1:09 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-03 18:29 John Treubig
2006-01-03 18:58 ` Alan Cox
2006-01-03 19:27 ` John Treubig
2006-01-03 21:48 ` Alan Cox
2006-01-04 12:37 ` Erik Slagter
2006-01-04 12:45 ` Alan Cox
2006-01-04 12:48 ` Erik Slagter
2006-01-05 20:27 John Treubig
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=1135213756.10383.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jtreubig@hotmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=raw@dslr.net \
/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).