From: Niklas Cassel <cassel@kernel.org>
To: shao.mingyin@zte.com.cn
Cc: dlemoal@kernel.org, linux-ide@vger.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: Fri, 13 Nov 2026 19:19:04 +0100 [thread overview]
Message-ID: <avdUmHKYnEyju1N1@ryzen> (raw)
In-Reply-To: <20261114020305026WLIRBj8VPB4JcDv_dhOQO@zte.com.cn>
Hello Shao,
On Sat, Nov 14, 2026 at 02:03:05AM +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.
>
> Each patch touches one driver, except patch 3, which covers the QorIQ
> and Seattle AHCI platform drivers. The patches are independent and any
> subset can be applied; the order lists the more severe failures first.
>
> All five patches carry QEMU A/B test descriptions after the --- line.
>
> This is a resend of [1]. Patches 1/5 and 3/5 lost their final
> context line in transport, so git apply reported a corrupt patch;
> 5/5 had the same trailing line. The diff content is unchanged; all
> five patches now end with the format-patch signature, which keeps the
> blank context line in place. Sorry for the noise.
>
> [1] https://lore.kernel.org/all/20261112221230052E8YTrPU5pi8AJJy6dnh9E@zte.com.cn/
>
> Shao Mingyin (5):
> ata: pata_ixp4xx_cf: avoid recursive locking in the PIO callback
> ata: pata_buddha: propagate host activation errors
> ata: ahci: release QorIQ and Seattle platform resources on removal
> ata: pata_ftide010: stop only successfully started Gemini bridges
> ata: ahci_seattle: serialize SGPIO register updates
>
> drivers/ata/ahci_qoriq.c | 2 +-
> drivers/ata/ahci_seattle.c | 8 ++++----
> drivers/ata/pata_buddha.c | 6 ++----
> drivers/ata/pata_ftide010.c | 37 +++++++++++++++++++------------------
> drivers/ata/pata_ixp4xx_cf.c | 5 +----
> 5 files changed, 27 insertions(+), 31 deletions(-)
>
> ---
> base-commit: ddfe51b0a0f5dc9e415cc2c8ad8db17532dd426b
This series looks good to me.
Unless any review comment shows up, I will apply it early next week.
Kind regards,
Niklas
prev parent reply other threads:[~2026-11-13 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 18:03 [PATCH RESEND 0/5] ata: fix platform driver probe, removal and locking issues 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 ` 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=avdUmHKYnEyju1N1@ryzen \
--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 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.