| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <44CD3F1E.1010101@s5r6.in-berlin.de> Date: Mon, 31 Jul 2006 01:22:06 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Johannes Weiner <hnazfoo@...glemail.com> CC: linux-kernel@...r.kernel.org, Patrick Mau <mau@...ar.ping.de> Subject: Re: Question about "Not Ready" SCSI error Johannes Weiner wrote: > On Sun, Jul 30, 2006 at 08:10:19PM +0200, Patrick Mau wrote: >> Google revealed[1] that the drive is waiting for a START UNIT command, >> but it seems that the kernel is not attempting to spin up the drive >> again. > > I don't know exactly if it's enough to requeue the scsi command, please > comment on this, guys. AFAIU, the scsi_eh (error handler) already has proper code for exactly this purpose, but the code is inactive. Any driver (SCSI low-level driver or SCSI command set driver) can activate it by setting scsi_device->allow_restart = 1. Brian King posted a patch which lets you enable that flag at runtime: "scsi: Add allow_restart sysfs class attribute", 2006-06-27 http://marc.theaimsgroup.com/?l=linux-scsi&m=115142503103468 The patch is in Linus' tree now. http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/scsi/sd.c -- Stefan Richter -=====-=-==- -=== ===== http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists