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: <311601c90701251321s58c8c0e2s9050fbf9c41cabad@mail.gmail.com>
Date:	Thu, 25 Jan 2007 14:21:48 -0700
From:	"Eric D. Mudama" <edmudama@...il.com>
To:	"Henrique de Moraes Holschuh" <hmh@....eng.br>
Cc:	"Soeren Sonnenburg" <kernel@....de>,
	"Tejun Heo" <htejun@...il.com>, "Jeff Garzik" <jeff@...zik.org>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: SATA hotplug from the user side ?

On 1/24/07, Henrique de Moraes Holschuh <hmh@....eng.br> wrote:
> Tejun, is it feasible to teach libata to check the device power management
> state before issuing any of the sleep, head unload and spin-down commands?
>
> libata would need to block its EH from resetting a channel for this check
> operation (we don't want to wake up sleeping devices to ask it if it is
> sleeping...) if it cannot easily check if an device is asleep before issuing
> a command to it.   Either that, or (for as long as there is no such a thing
> as a multi-initiator libata device) just keep track of the device power
> management state by snooping all the commands sent to it.

In the ATA spec, the CHECK POWER MODE command (E5h) specifically
states that it shouldn't alter the power mode of the device.
Therefore, there should be no harm in checking the power mode of a
device in STANDBY or IDLE state, and it shouldn't cause the device to
spin up.  Checking a drive on my bench I confirmed this behavior.

With Serial ATA you have to consider the SATA bus PM states as well,
but that's a different topic of discussion.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ