From: Phillip Susi <psusi@cfl.rr.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Tejun Heo <tj@kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Jeff Garzik <jgarzik@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata: implement on-demand HPA unlocking
Date: Thu, 10 Feb 2011 14:20:43 -0500 [thread overview]
Message-ID: <4D543A8B.7040504@cfl.rr.com> (raw)
In-Reply-To: <AANLkTikL6rGvg7PeCzJPAaWm9-4dniCY4NErGUgi_54N@mail.gmail.com>
On 2/10/2011 7:49 AM, Bartlomiej Zolnierkiewicz wrote:
> no way for kernel alone to get all different cases right. The best we
> can do is export all data points to user-space and let it & user deal
> with the resulting mess..
Is it even possible to turn the HPA back on when udev runs dmraid? I
suppose that would fix the problems with dmraid.
What worries me though is that while it seems that most systems so far
do not seem to store anything vital in the HPA so unlocking by default
does not cause harm, it is defined as a feature, not a bug, so future
systems can very well start storing vital data there, and then we really
will step in it by always unlocking.
next prev parent reply other threads:[~2011-02-10 19:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 20:23 libata: implement on-demand HPA unlocking Phillip Susi
2011-02-09 8:59 ` Tejun Heo
2011-02-09 15:20 ` Phillip Susi
2011-02-09 15:37 ` Alan Cox
2011-02-09 15:36 ` Tejun Heo
2011-02-09 18:48 ` Jeff Garzik
2011-02-09 19:45 ` Phillip Susi
2011-02-10 9:44 ` Tejun Heo
2011-02-10 18:47 ` Phillip Susi
2011-02-10 19:07 ` Tejun Heo
2011-02-09 19:39 ` Phillip Susi
2011-02-09 19:36 ` Phillip Susi
2011-02-09 20:47 ` Greg Freemyer
2011-02-09 21:12 ` Phillip Susi
2011-02-09 21:13 ` Alan Cox
2011-02-09 21:28 ` Phillip Susi
2011-02-09 21:39 ` Alan Cox
2011-02-10 0:23 ` Phillip Susi
2011-02-10 12:46 ` Alan Cox
2011-02-10 18:58 ` Phillip Susi
2011-02-10 19:19 ` Tejun Heo
2011-02-11 18:16 ` Phillip Susi
2011-02-10 12:49 ` Bartlomiej Zolnierkiewicz
2011-02-10 19:20 ` Phillip Susi [this message]
2011-02-10 19:35 ` Alan Cox
2011-02-11 18:22 ` Phillip Susi
2011-02-10 19:37 ` Alan Cox
2011-02-09 21:41 ` Tejun Heo
2011-02-10 0:35 ` Phillip Susi
2011-02-10 1:46 ` Robert Hancock
2011-02-10 9:13 ` Tejun Heo
2011-02-10 19:11 ` Phillip Susi
2011-02-10 19:31 ` Alan Cox
2011-02-11 18:18 ` Phillip Susi
2011-02-11 18:25 ` Alan Cox
2011-02-11 18:38 ` Phillip Susi
2011-02-10 19:32 ` Tejun Heo
2011-02-10 19:34 ` Tejun Heo
2011-02-11 18:30 ` Phillip Susi
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=4D543A8B.7040504@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@decadent.org.uk \
--cc=bzolnier@gmail.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.org \
/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).