| 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: <47BF3E54.9050609@rtr.ca> Date: Fri, 22 Feb 2008 16:27:48 -0500 From: Mark Lord <liml@....ca> To: Matthew Wilcox <matthew@....cx> Cc: linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: ata_ram driver Matthew Wilcox wrote: > I've ported the scsi_ram driver [1] to libata. It could use a lot more > work -- there's a lot of stuff in the identify page that I haven't > filled in, and there's a lot of commands it doesn't even try to execute. > > For example, when you unload the driver, you get the mildly disturbing > messages: > > sd 12:0:0:0: [sdb] Stopping disk > sd 12:0:0:0: [sdb] START_STOP FAILED > sd 12:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK > .. I see messages like those with *established* libata drivers from time to time. It could just be a bug in the shutdown sequence, somewhere between libata, SCSI, block layer, and the device model in general. Or not. Cheers -- 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