From: Niklas Cassel <cassel@kernel.org>
To: dlemoal@kernel.org, linux-ide@vger.kernel.org, shao.mingyin@zte.com.cn
Cc: Niklas Cassel <cassel@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH RESEND 0/5] ata: fix platform driver probe, removal and locking issues
Date: Mon, 16 Nov 2026 17:18:09 +0100 [thread overview]
Message-ID: <179484577325.2781504.2497197768299979233.b4-ty@kernel.org> (raw)
In-Reply-To: <20261114020305026WLIRBj8VPB4JcDv_dhOQO@zte.com.cn>
On Sat, 14 Nov 2026 02:03:05 +0800, shao.mingyin@zte.com.cn wrote:
> The ATA platform drivers in this series have independent defects in
> their probe, removal or locking paths. They share the same shape:
> state established in probe is not checked, torn down or serialized
> consistently.
>
> Patch 1 fixes recursive locking in the IXP4xx CF PIO callback, which
> can hang the first data transfer, including IDENTIFY during probe. Patch 2
> returns the host activation error from the Buddha probe path instead of
> reporting a successful bind. Patch 3 makes the QorIQ and Seattle
> drivers inherit ahci_platform_ops so that host teardown runs host_stop.
> Patch 4 stops only the Gemini SATA bridges that started successfully.
> Patch 5 serializes the controller-wide SGPIO update in the Seattle LED
> callback.
>
> [...]
Applied to libata/linux.git (for-7.5), thanks!
[1/5] ata: pata_ixp4xx_cf: avoid recursive locking in the PIO callback
https://git.kernel.org/libata/linux/c/5149ef22
[2/5] ata: pata_buddha: propagate host activation errors
https://git.kernel.org/libata/linux/c/5849257c
[3/5] ata: ahci: release QorIQ and Seattle platform resources on removal
https://git.kernel.org/libata/linux/c/8d1ddc50
[4/5] ata: pata_ftide010: stop only successfully started Gemini bridges
https://git.kernel.org/libata/linux/c/1c72150a
[5/5] ata: ahci_seattle: serialize SGPIO register updates
https://git.kernel.org/libata/linux/c/e83e9d4d
Kind regards,
Niklas
prev parent reply other threads:[~2026-11-16 16:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 18:03 shao.mingyin
2026-11-13 18:03 ` [PATCH RESEND 1/5] ata: pata_ixp4xx_cf: avoid recursive locking in the PIO callback shao.mingyin
2026-11-13 18:03 ` [PATCH RESEND 2/5] ata: pata_buddha: propagate host activation errors shao.mingyin
2026-11-13 18:03 ` [PATCH RESEND 3/5] ata: ahci: release QorIQ and Seattle platform resources on removal shao.mingyin
2026-11-13 18:03 ` [PATCH RESEND 4/5] ata: pata_ftide010: stop only successfully started Gemini bridges shao.mingyin
2026-11-13 18:03 ` [PATCH RESEND 5/5] ata: ahci_seattle: serialize SGPIO register updates shao.mingyin
2026-11-13 18:19 ` [PATCH RESEND 0/5] ata: fix platform driver probe, removal and locking issues Niklas Cassel
2026-11-15 2:05 ` Damien Le Moal
2026-11-16 16:18 ` Niklas Cassel [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=179484577325.2781504.2497197768299979233.b4-ty@kernel.org \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shao.mingyin@zte.com.cn \
--cc=stable@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
all inboxes | Powered by JetHome®