From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: ATA Write Error and Time-out Notification in User Space Date: Thu, 22 Dec 2005 01:09:16 +0000 Message-ID: <1135213756.10383.9.camel@localhost.localdomain> References: <1135119036.25010.21.camel@localhost.localdomain> <200512201831.38592.raw@dslr.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200512201831.38592.raw@dslr.net> Sender: linux-ide-owner@vger.kernel.org To: Drew Winstel Cc: linux-ide@vger.kernel.org, John Treubig , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org List-Id: linux-scsi@vger.kernel.org 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