linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: "Rus V. Brushkoff" <rus@SoyuzKT.Od.UA>,
	Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org
Subject: Re: SATA HDD password problem
Date: Sat, 08 Mar 2008 09:51:40 +0900	[thread overview]
Message-ID: <47D1E31C.3020109@gmail.com> (raw)
In-Reply-To: <47D154F0.50607@rtr.ca>

Mark Lord wrote:
>>>  Hmm, if someone enable SSP in the drive after password unlock - does
>>> this mean that it will be unlocked forever ? Or drive can distinguish
>>> between power-on and hard-reset states ?
>>
>> SSP by default stays on, so once unlocked it will stay unlocked as long
>> as power stays applied.  On power loss, it gets locked again.  On
>> reboots, the BIOS can always lock it again if it wants to.
> ..
> 
> The problem here, is that SSP itself gets turned-OFF after COMMRESET.
> It does preserve settings over the COMMRESET, but it then has to be
> renewed (re-issued by the driver) for things to survive a subsequent
> COMMRESET after the first one.   This has to go into libata,
> as it's not something we can control entirely from hdparm.

The following is from ACS8 SSP feature set description.

  Software settings preservation may be enabled or disabled using SET
  FEATURES with a Count field of 06h. If a device supports software
  settings preservation, the feature shall be enabled by default.  See
  SATA 2.6 for more information.

And the following is from enable/disable SSP description (7.48.18.7).

  The enable/disable state for software settings preservation shall
  persist across software reset. The enable/disable state for software
  settings preservation shall be reset to its default state upon
  COMRESET. The host may disable software settings preservation in
  order to not preserve software settings across COMRESET.

So, the default state being enabled and COMRESET always returning it
to default.  I don't think libata needs to take further action.

Thanks.

-- 
tejun

      reply	other threads:[~2008-03-08  0:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  9:50 SATA HDD password problem Rus V. Brushkoff
2008-03-05 12:30 ` Jeff Garzik
2008-03-05 12:49   ` Rus V. Brushkoff
2008-03-06  9:47     ` Tejun Heo
2008-03-06 12:31       ` Rus V. Brushkoff
2008-03-07  3:54         ` Tejun Heo
2008-03-07  9:17           ` Rus V. Brushkoff
2008-03-08  1:17             ` Tejun Heo
2008-03-08 16:12               ` Rus V. Brushkoff
2008-03-09  5:13                 ` Tejun Heo
2008-03-09  5:13                   ` Tejun Heo
2008-03-09 17:42                     ` Rus V. Brushkoff
2008-03-10  0:37                       ` Tejun Heo
2008-03-10  1:25                       ` [PATCH #upstream-fixes] ahci: implement skip_host_reset parameter Tejun Heo
2008-03-17 12:27                         ` Jeff Garzik
2008-03-07 14:45           ` SATA HDD password problem Mark Lord
2008-03-08  0:51             ` Tejun Heo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47D1E31C.3020109@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=rus@SoyuzKT.Od.UA \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).