linux-kernel - Re: Power management for SCSI

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.44L0.0808131051330.2455-100000@iolanthe.rowland.org>
Date:	Wed, 13 Aug 2008 10:59:23 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Oliver Neukum <oneukum@...e.de>
cc:	Pavel Machek <pavel@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	Linux-pm mailing list <linux-pm@...ts.osdl.org>,
	<James.Bottomley@...senpartnership.com>, <teheo@...ell.com>
Subject: Re: Power management for SCSI

On Wed, 13 Aug 2008, Oliver Neukum wrote:

> Very well. I see a basic problem here. For USB it is necessary that child
> devices be suspended before anything higher up in the tree is suspended.
> SATA seems to be able to power down a link while the device is not suspended.

Is the USB transport unique in its requirement that all the child
devices must be suspended before the link can be powered down?  Maybe 
that requirement should be made an explicit property of the transport 
or the transport class.

> In fact in true SCSI busses can be shared. So are we using the correct
> approach?

This is a good question.  Most USB mass-storage devices do not act as a
true SCSI bus, but I believe there are a few non-standard ones that do
-- the USB device really contains a SCSI host and arbitrary SCSI
targets can be attached to it.  For the moment, we should be safe
enough using a model in which there are no other initiators on a
USB-type SCSI transport, but it's something to keep in mind.

Alan Stern

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