From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: relax checks in ata_read_log_directory()
Date: Thu, 9 Oct 2025 14:16:02 +0200 [thread overview]
Message-ID: <aOenggZ92Af3tvBc@ryzen> (raw)
In-Reply-To: <20251009104600.523444-1-dlemoal@kernel.org>
On Thu, Oct 09, 2025 at 07:46:00PM +0900, Damien Le Moal wrote:
> Commit 6d4405b16d37 ("ata: libata-core: Cache the general purpose log
> directory") introduced caching of a device general purpose log directory
> to avoid repeated access to this log page during device scan. This
> change also added a check on this log page to verify that the log page
> version is 0x0001 as mandated by the ACS specifications.
>
> And it turns out that some devices do not bother reporting this version,
> instead reporting a version 0, resulting in error messages such as:
>
> ata6.00: Invalid log directory version 0x0000
>
> and to the device being marked as not supporting the general purpose log
> directory log page.
>
> Since before commit 6d4405b16d37 the log page version check did not
> exist and things were still working correctly for these devices, relax
> ata_read_log_directory() version check and only warn about the invalid
> log page version number without disabling access to the log directory
> page.
>
> Fixes: 6d4405b16d37 ("ata: libata-core: Cache the general purpose log directory")
> Cc: stable@vger.kernel.org
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=220635
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Looks good, will queue up after -rc1.
Kind regards,
Niklas
next prev parent reply other threads:[~2025-10-09 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 10:46 [PATCH] ata: libata-core: relax checks in ata_read_log_directory() Damien Le Moal
2025-10-09 12:16 ` Niklas Cassel [this message]
2025-10-13 7:31 ` 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=aOenggZ92Af3tvBc@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--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