linux-kernel - Re: ata

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 06 Mar 2008 09:28:21 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Tejun Heo <htejun@...il.com>
Cc:	Mark Lord <liml@....ca>, Matthew Wilcox <matthew@....cx>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ata_ram driver

On Thu, 2008-03-06 at 17:21 +0900, Tejun Heo wrote:
> Mark Lord wrote:
> > 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.
> 
> It's because of the sequence of events.  Currently, driver unload
> sequence is the same as when the device is hot unplugged.  libata
> detects that the device is gone and disables it and report it to SCSI
> layer.  SCSI layer takes over and tries to kill the SCSI device and tell
> sd to shutdown and sd issues START_STOP to shutdown which fails w/
> DID_BAD_TARGET because the matching ATA device is already gone.  I've
> left it that way because I'm not sure whether spinning down the drive on
> driver unload is the correct thing to do.  The message is annoying tho.

Um, it's not supposed to happen that way.  Your signal that a disk is
gone is slave destroy ... and we don't call that until after the target
has been processed.  Devices are supposed to stay online (if possible)
from slave alloc to slave destroy.

James


--
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/