All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jgarzik@pobox.com>, Jacob <fun2program8@yahoo.com>,
	Christopher Hogan <chris.c.hogan@gmail.com>,
	Robert Hancock <hancockrwd@gmail.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] libata: add warning about possible HPA compatibility issue
Date: Tue, 26 May 2009 01:15:00 +0200	[thread overview]
Message-ID: <200905260115.00794.bzolnier@gmail.com> (raw)
In-Reply-To: <20090525233814.4cb8b1c2@lxorguk.ukuu.org.uk>

On Tuesday 26 May 2009 00:38:14 Alan Cox wrote:
> > > NAK - this is extremely misleading and will just randomly terrify users,
> > > who may then set the paramater and corrupt things like BIOS save areas.
> > 
> > Please propose better description.
> 
> As was discussed before
> 
> Tejun has a patch in the queue which exposes the HPA and real sizes to
> the OS

In queue for 2.6.30?

> Libata can support revalidating a disc
> 
> Once the HPA/Real size data is there the tools can be tuned for this and
> a sysfs node added to switch hpa on/off per disc. At that point this can
> be done by the user space intelligently.

Unless you happen to have partition with tools in HPA area etc.

Also care to post link to the existing user-space tools with added HPA
support and documentation how to use them so I can start pointing people
reporting problems in this direction?

> The fact this is a user parameter is itself a problem.

Yes.  It is a problem but we can't reverse the history.

I fully agree w.r.t to proper handling of HPA but we need "something" in
the meantime because it is *real* issue resulting in *real* users filling
*real* bug-reports (which unfortunately always get assigned to me first
so I'm needlessly wasting my time on them).

IOW Please stop downplaying bug #13365 which this patch tries to alleviate.

I'm adding Andrew to cc:...

  reply	other threads:[~2009-05-25 23:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-25 21:48 [PATCH] libata: add warning about possible HPA compatibility issue Bartlomiej Zolnierkiewicz
2009-05-25 22:20 ` Alan Cox
2009-05-25 22:36   ` Bartlomiej Zolnierkiewicz
2009-05-25 22:38     ` Alan Cox
2009-05-25 23:15       ` Bartlomiej Zolnierkiewicz [this message]
2009-05-25 23:16         ` Alan Cox

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=200905260115.00794.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=chris.c.hogan@gmail.com \
    --cc=fun2program8@yahoo.com \
    --cc=hancockrwd@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.