From: Ben Hutchings <ben@decadent.org.uk>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: Working around bogus HPAs in libata
Date: Tue, 06 Apr 2010 03:28:50 +0100 [thread overview]
Message-ID: <1270520930.24287.102.camel@localhost> (raw)
In-Reply-To: <4BBA95F8.7070909@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
On Tue, 2010-04-06 at 11:01 +0900, Tejun Heo wrote:
> Hello,
>
> On 04/03/2010 06:57 AM, Ben Hutchings wrote:
> > Several distributions have turned on the switch by default. As I said
> > previously, this turned out to be a bad idea.
>
> Heh, yeah, I did that on openSUSE which was mandatory for backward
> compatibility because ide unlocked HPA by default (at least on
> openSUSE). Do you know how common are these problem cases w/ default
> HPA unlocking?
No idea, but they look serious enough to worry about.
> Diddling with HPAs and writing stuff to disks from
> BIOS is generally a very bad idea because it means that switching BIOS
> options or attaching a hard drive to a different motherboard can lead
> to data corruption.
If a system vendor puts its own name or model numbers on the disks it
ships then I think the BIOS or other platform firmware can reasonably
assume that it 'owns' and can write to the HPA on a disk with the
vendor's identification. (I wouldn't be at all surprised to find that
some vendors take shortcuts though.)
[...]
> > My test case also revealed a bug in the partition scanning retry:
> > partition 2 is an extended partition and wholly within the HPA, so the
> > extended partition table is not accessible until the HPA is disabled.
> > But it is not rescanned after the HPA is disabled. However, this is is
> > consistent between IDE and libata drivers and will not be a regression
> > when making the transition.
>
> Ah... I see, but let's fix that up too. It could be worse to have
> half working workaround than not working around at all. I'll update
> the patch once the currently pending HPA updates are in.
Oh, what are those?
I want to apply some version of this fix in Debian soon so we can
complete the transition to libata. I would very much appreciate it if
you could answer whether or not the multiple 'capacity change' messages
may indicate a problem.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2010-04-06 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 17:25 Working around bogus HPAs in libata Ben Hutchings
2010-04-02 3:24 ` Tejun Heo
2010-04-02 21:57 ` Ben Hutchings
2010-04-06 2:01 ` Tejun Heo
2010-04-06 2:28 ` Ben Hutchings [this message]
2010-04-06 2:33 ` Tejun Heo
2010-04-24 2:26 ` Ben Hutchings
2010-04-24 5:35 ` Tejun Heo
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=1270520930.24287.102.camel@localhost \
--to=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--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).