From: Damien Le Moal <dlemoal@kernel.org>
To: TJ Adams <tadamsjr@google.com>, Niklas Cassel <cassel@kernel.org>,
Hannes Reinecke <hare@suse.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Igor Pylypiv <ipylypiv@google.com>,
Salomon Dushimirimana <salomondush@google.com>
Subject: Re: [PATCH v2 0/2] Fixes for security locked drives
Date: Wed, 8 Jul 2026 13:53:15 +0900 [thread overview]
Message-ID: <e9f103e8-6b6b-476a-8064-fb8d0bbf7506@kernel.org> (raw)
In-Reply-To: <20260706210054.1336654-1-tadamsjr@google.com>
On 7/7/26 06:00, TJ Adams wrote:
> These patches improve libata handling of locked drives.
>
> Changes since v1:
> - Simplified the n_sectors check in ata_dev_revalidate() as suggested by
> Niklas
> - Added Patch 2 to disable HPA resizing for locked drives to address
> Sashiko's feedback.
>
> Testing:
> - Verified using the internal test suite that originally detected the regression.
> - The issue can be reproduced manually using the steps outlined in the thread
> (runtime locking, disabling SSP, active I/O, and link reset).
Applied to for-7.2-fixes. Thanks!
Note: I added Cc:stable tag to both patches.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2026-07-08 4:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 18:28 [PATCH] ata: libata-core: Allow capacity transition to zero for locked drives TJ Adams
2026-06-22 18:40 ` sashiko-bot
2026-06-24 14:20 ` Niklas Cassel
2026-07-01 23:16 ` TJ Adams
2026-07-02 15:43 ` Niklas Cassel
2026-07-06 21:00 ` [PATCH v2 0/2] Fixes for security " TJ Adams
2026-07-06 21:00 ` [PATCH v2 1/2] ata: libata-core: Skip HPA resize for " TJ Adams
2026-07-07 6:02 ` Damien Le Moal
2026-07-07 17:01 ` TJ Adams
2026-07-08 1:38 ` Damien Le Moal
2026-07-06 21:00 ` [PATCH v2 2/2] ata: libata-core: Allow capacity transition to zero " TJ Adams
2026-07-08 4:53 ` Damien Le Moal [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=e9f103e8-6b6b-476a-8064-fb8d0bbf7506@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=hare@suse.de \
--cc=ipylypiv@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=salomondush@google.com \
--cc=tadamsjr@google.com \
/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