Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Nicolin Chen" <nicolinc@nvidia.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v5 08/18] iommu/arm-smmu-v3: Skip remaining GERROR causes on SFM
Date: Fri, 03 Jul 2026 04:29:45 +0000	[thread overview]
Message-ID: <20260703042945.EF1211F000E9@smtp.kernel.org> (raw)
In-Reply-To: <87ac4c46207f8e9903cc6a6f6f1b46995145cb64.1783044582.git.nicolinc@nvidia.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] Calling `arm_smmu_device_disable()` from the `arm_smmu_gerror_handler` hardirq handler triggers a sleep-in-atomic BUG because it polls a register with a non-zero sleep delay.
--

commit 1a84214c7c4ffc13f27088bf53ea902723185640
Author: Nicolin Chen <nicolinc@nvidia.com>

iommu/arm-smmu-v3: Skip remaining GERROR causes on SFM

When the SMMU enters Service Failure Mode (SFM), the remaining GERROR
causes are skipped and acked early since the SMMU is being disabled.

> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> index da29e523d78b7..8a4edefeec770 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> @@ -2315,8 +2315,11 @@ static irqreturn_t arm_smmu_gerror_handler(int irq, void *dev)
>  		 active);
>  
>  	if (active & GERROR_SFM_ERR) {
> +		/* SMMU is being disabled, so other errors don't matter */
> +		writel(gerror, smmu->base + ARM_SMMU_GERRORN);
>  		dev_err(smmu->dev, "device has entered Service Failure Mode!\n");
>  		arm_smmu_device_disable(smmu);

[Severity: High]
This is a pre-existing issue, but does calling arm_smmu_device_disable()
from the arm_smmu_gerror_handler() hardirq handler trigger a 
sleep-in-atomic BUG?

arm_smmu_device_disable() eventually calls arm_smmu_write_reg_sync(),
which uses readl_relaxed_poll_timeout() with a 1us delay:

drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:arm_smmu_write_reg_sync() {
    ...
    return readl_relaxed_poll_timeout(smmu->base + ack_off, reg, reg == val,
                                      1, ARM_SMMU_POLL_TIMEOUT_US);
}

The polling macro invokes might_sleep_if(1) and usleep_range(), which isn't
safe in hardirq context.

> +		return IRQ_HANDLED;
>  	}
>  
>  	if (active & GERROR_MSI_GERROR_ABT_ERR)

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1783044582.git.nicolinc@nvidia.com?part=8

  reply	other threads:[~2026-07-03  4:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  4:06 [PATCH v5 00/18] iommu/arm-smmu-v3: Quarantine device upon ATC invalidation timeout Nicolin Chen
2026-07-03  4:06 ` [PATCH v5 01/18] PCI: Don't suspend IOMMU when probing reset capability Nicolin Chen
2026-07-03  4:27   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 02/18] PCI/CXL: Probe the underlying bus reset in cxl_reset_bus_function() Nicolin Chen
2026-07-03  4:29   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 03/18] PCI: Propagate FLR return values to callers Nicolin Chen
2026-07-03  4:25   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 04/18] iommu: Convert gdev->blocked from bool to enum gdev_blocked Nicolin Chen
2026-07-03  4:24   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 05/18] iommu: Pass in reset result to pci_dev_reset_iommu_done() Nicolin Chen
2026-07-03  4:27   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 06/18] iommu/arm-smmu-v3: Don't rb_erase() a never-inserted stream node Nicolin Chen
2026-07-03  4:25   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 07/18] iommu/arm-smmu-v3: Mark ATC invalidate timeouts via lockless bitmap Nicolin Chen
2026-07-03  4:26   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 08/18] iommu/arm-smmu-v3: Skip remaining GERROR causes on SFM Nicolin Chen
2026-07-03  4:29   ` sashiko-bot [this message]
2026-07-03  4:06 ` [PATCH v5 09/18] iommu/arm-smmu-v3: Introduce per-cmdq cmdq_err_handler callback Nicolin Chen
2026-07-03  4:32   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 10/18] iommu/arm-smmu-v3: Recheck CMDQ_ERR in tegra241_vintf0_handle_error() Nicolin Chen
2026-07-03  4:40   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 11/18] iommu/arm-smmu-v3: Co-clear pending CMDQ_ERR when CMD_SYNC times out Nicolin Chen
2026-07-03  4:39   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 12/18] iommu/arm-smmu-v3: Introduce arm_smmu_cmdq_batch_issue() wrapper Nicolin Chen
2026-07-03  4:22   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 13/18] iommu/arm-smmu-v3: Add streams_lock for atomic-context SID->master lookup Nicolin Chen
2026-07-03  4:26   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 14/18] iommu/arm-smmu-v3: Add has_ats to struct arm_smmu_cmdq_batch Nicolin Chen
2026-07-03  4:29   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 15/18] iommu/arm-smmu-v3: Add INV_TYPE_ATS_BROKEN to skip quarantined ATS masters Nicolin Chen
2026-07-03  4:34   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 16/18] iommu/arm-smmu-v3: Factor out CMDQ batch force-sync conditions Nicolin Chen
2026-07-03  4:29   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 17/18] iommu/arm-smmu-v3: Thread arm_smmu_master_domain on a per-master list Nicolin Chen
2026-07-03  4:32   ` sashiko-bot
2026-07-03  4:06 ` [PATCH v5 18/18] iommu/arm-smmu-v3: Block ATS for a master upon an ATC invalidation timeout Nicolin Chen
2026-07-03  4:36   ` 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=20260703042945.EF1211F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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