From: Ethan Zhao <haifeng.zhao@linux.intel.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>,
dwmw2@infradead.org, baolu.lu@linux.intel.com, joro@8bytes.org,
will@kernel.org, robin.murphy@arm.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/vt-d: fix system hang on reboot -f
Date: Fri, 21 Feb 2025 16:40:39 +0800 [thread overview]
Message-ID: <ba2a6295-7983-4701-8c42-797efe22ecb7@linux.intel.com> (raw)
In-Reply-To: <20250220101511.37602-1-cuiyunhui@bytedance.com>
在 2025/2/20 18:15, Yunhui Cui 写道:
> When entering intel_iommu_shutdown, system interrupts are disabled,
System interrupts were disabled ? you mean all interrupts were disabled
when entering intel_iommu_shutdown(), perhaps it is not true, at least
for upstream latest code.
> and the reboot process might be scheduled out by down_write(). If the
> scheduled process does not yield (e.g., while(1)), the system will hang.
No NMI lockup watchdog jumping out here ?
Thanks,
Ethan
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> ---
> drivers/iommu/intel/iommu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
> index cc46098f875b..76a1d83b46bf 100644
> --- a/drivers/iommu/intel/iommu.c
> +++ b/drivers/iommu/intel/iommu.c
> @@ -2871,7 +2871,8 @@ void intel_iommu_shutdown(void)
> if (no_iommu || dmar_disabled)
> return;
>
> - down_write(&dmar_global_lock);
> + if (!down_write_trylock(&dmar_global_lock))
> + return;
>
> /* Disable PMRs explicitly here. */
> for_each_iommu(iommu, drhd)
--
"firm, enduring, strong, and long-lived"
next prev parent reply other threads:[~2025-02-21 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 10:15 [PATCH] iommu/vt-d: fix system hang on reboot -f Yunhui Cui
2025-02-21 8:40 ` Ethan Zhao [this message]
2025-02-21 9:46 ` [External] " yunhui cui
2025-02-24 2:53 ` Ethan Zhao
2025-02-24 3:21 ` Ethan Zhao
2025-02-24 1:02 ` Baolu Lu
2025-02-24 3:42 ` [External] " yunhui cui
2025-02-24 5:37 ` Ethan Zhao
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=ba2a6295-7983-4701-8c42-797efe22ecb7@linux.intel.com \
--to=haifeng.zhao@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=cuiyunhui@bytedance.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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