From: Rosen Penev <rosenp@gmail.com>
To: linux-ide@vger.kernel.org
Cc: Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
Jeff Garzik <jgarzik@redhat.com>,
Prodyut Hazarika <phazarika@appliedmicro.com>,
Mark Miesfeld <mmiesfeld@appliedmicro.com>,
Rupjyoti Sarmah <rsarmah@amcc.com>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCHv3 5/5] ata: sata_dwc_460ex: disable SATA interrupts on device removal
Date: Wed, 8 Jul 2026 19:32:02 -0700 [thread overview]
Message-ID: <20260709023202.2132165-6-rosenp@gmail.com> (raw)
In-Reply-To: <20260709023202.2132165-1-rosenp@gmail.com>
sata_dwc_remove() fails to mask the controller's INTMR and ERRMR
registers before tearing down the host. If the hardware asserts an
interrupt during teardown (after ata_host_detach() but before the
IRQ handler is unregistered by devres), this can trigger an unhandled
interrupt storm and potentially lock up the system.
Add sata_dwc_disable_interrupts() and call it at the beginning of
sata_dwc_remove(), before ata_host_detach().
Fixes: 62936009f35a ("[libata] Add 460EX on-chip SATA driver, sata_dwc_460ex"
Assisted-by: opencode:big-pickle
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
drivers/ata/sata_dwc_460ex.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/ata/sata_dwc_460ex.c b/drivers/ata/sata_dwc_460ex.c
index 08d40e287bac..381ace5d33e1 100644
--- a/drivers/ata/sata_dwc_460ex.c
+++ b/drivers/ata/sata_dwc_460ex.c
@@ -752,6 +752,14 @@ static int sata_dwc_qc_complete(struct ata_port *ap, struct ata_queued_cmd *qc)
return 0;
}
+static void sata_dwc_disable_interrupts(struct sata_dwc_device *hsdev)
+{
+ sata_dwc_writel(&hsdev->sata_dwc_regs->intmr, 0);
+ sata_dwc_writel(&hsdev->sata_dwc_regs->errmr, 0);
+ /* Flush posted writes */
+ sata_dwc_readl(&hsdev->sata_dwc_regs->intpr);
+}
+
static void sata_dwc_enable_interrupts(struct sata_dwc_device *hsdev)
{
/* Enable selective interrupts by setting the interrupt maskregister*/
@@ -1203,6 +1211,8 @@ static void sata_dwc_remove(struct platform_device *ofdev)
struct ata_host *host = dev_get_drvdata(dev);
struct sata_dwc_device *hsdev = host->private_data;
+ sata_dwc_disable_interrupts(hsdev);
+
ata_host_detach(host);
phy_exit(hsdev->phy);
--
2.55.0
next prev parent reply other threads:[~2026-07-09 2:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 2:31 [PATCHv3 0/5] ata: sata_dwc_460ex: cleanups and interrupt ordering fix Rosen Penev
2026-07-09 2:31 ` [PATCHv3 1/5] ata: sata_dwc_460ex: use platform_get_irq() Rosen Penev
2026-07-09 2:47 ` sashiko-bot
2026-07-09 5:23 ` Rosen Penev
2026-07-09 2:31 ` [PATCHv3 2/5] ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered Rosen Penev
2026-07-09 2:32 ` [PATCHv3 3/5] ata: sata_dwc_460ex: fix clear_interrupt_bit() clearing all pending interrupts Rosen Penev
2026-07-09 2:32 ` [PATCHv3 4/5] ata: sata_dwc_460ex: fix infinite loop in NCQ tag completion bit-scanning Rosen Penev
2026-07-09 2:32 ` Rosen Penev [this message]
2026-07-09 2:55 ` [PATCHv3 5/5] ata: sata_dwc_460ex: disable SATA interrupts on device removal sashiko-bot
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=20260709023202.2132165-6-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmiesfeld@appliedmicro.com \
--cc=phazarika@appliedmicro.com \
--cc=rsarmah@amcc.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 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.