From: Damien Le Moal <dlemoal@kernel.org>
To: Ioannis Barkas <jnyb.de@gmail.com>, linux-ide@vger.kernel.org
Cc: IoannisBarkasjnyb.de@gmail.com, NickBarkasnickbgrk@gmail.com
Subject: Re: [PATCH] [PATCH v3] ata: libata-core: Correct HPA horkage
Date: Wed, 14 Oct 2026 07:44:11 +0200 [thread overview]
Message-ID: <5b5faa39-1590-45b9-8a4a-ee328c53e826@kernel.org> (raw)
In-Reply-To: <20261013201926.14456-1-jnyb.de@gmail.com>
On 2026/10/13 22:19, Ioannis Barkas wrote:
> Code wrongly detects disks using 2 specific serial numbers
> Use their firmware to detect whole family of affected disks
s/firmware/firmware version ?
>
> Fixes: 16c55b038033 (libata: implement BROKEN_HPA horkage and apply it to affected drives")
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=8888
> Signed-off-by: <Ioannis Barkas jnyb.de@gmail.com>
> Signed-off-by: <Nick Barkas nickbgrk@gmail.com>
> ---
> drivers/ata/libata-core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 59e87b987d..b23e1c3e4c 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -4248,8 +4248,8 @@ static const struct ata_dev_quirks_entry __ata_dev_quirks[] = {
>
> /* devices which puke on READ_NATIVE_MAX */
> { "HDS724040KLSA80", "KFAOA20N", ATA_QUIRK_BROKEN_HPA },
> - { "WDC WD3200JD-00KLB0", "WD-WCAMR1130137", ATA_QUIRK_BROKEN_HPA },
> - { "WDC WD2500JD-00HBB0", "WD-WMAL71490727", ATA_QUIRK_BROKEN_HPA },
> + { "WDC WD3200JD-00KLB0", "08.05J08", ATA_QUIRK_BROKEN_HPA },
> + { "WDC WD2500JD-00HBB0", "08.02D08", ATA_QUIRK_BROKEN_HPA },
> { "MAXTOR 6L080L4", "A93.0500", ATA_QUIRK_BROKEN_HPA },
>
> /* this one allows HPA unlocking but fails IOs on the area */
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-10-14 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 20:19 [PATCH] [PATCH v3] ata: libata-core: Correct HPA horkage Ioannis Barkas
2026-10-14 5:44 ` Damien Le Moal [this message]
2026-10-14 9:29 ` Niklas Cassel
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=5b5faa39-1590-45b9-8a4a-ee328c53e826@kernel.org \
--to=dlemoal@kernel.org \
--cc=IoannisBarkasjnyb.de@gmail.com \
--cc=NickBarkasnickbgrk@gmail.com \
--cc=jnyb.de@gmail.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox