From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
thomas.petazzoni@bootlin.com,
Zhenzhong Duan <zhenzhong.duan@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Joerg Roedel <joerg.roedel@amd.com>,
Miguel Gazquez <miguel.gazquez@bootlin.com>
Subject: Re: [PATCH 6.12.y] iommu/vt-d: Fix oops due to out of scope access
Date: Sun, 26 Jul 2026 08:04:48 -0400 [thread overview]
Message-ID: <20260725192000.stable-0009@kernel.org> (raw)
In-Reply-To: <20260723170133.2299823-1-miguel.gazquez@bootlin.com>
> commit a6dea58d8625c06b9654c0555f101742481335c3 upstream.
>
> The global static blocked domain is a dummy domain without corresponding
> dmar_domain structure, accessing beyond iommu_domain structure triggers
> oops easily.
Thanks for the backport, but I don't think 6.12 needs this one. The oops
is not reachable on 6.12: the blocked domain has no .set_dev_pasid, there
is no PASID-level replace path, and the FLR-reset flow that reaches the
remove-dev-pasid code with a blocked domain landed after 6.12. So the
added early-return would just be dead code there. The fix is already in
7.1 and 6.18 where the path does exist, so I'll drop this for 6.12.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-26 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 14:46 FAILED: patch "[PATCH] iommu/vt-d: Fix oops due to out of scope access" failed to apply to 6.12-stable tree gregkh
2026-07-23 17:01 ` [PATCH 6.12.y] iommu/vt-d: Fix oops due to out of scope access Miguel Gazquez
2026-07-26 12:04 ` Sasha Levin [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=20260725192000.stable-0009@kernel.org \
--to=sashal@kernel.org \
--cc=baolu.lu@linux.intel.com \
--cc=joerg.roedel@amd.com \
--cc=kevin.tian@intel.com \
--cc=miguel.gazquez@bootlin.com \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=zhenzhong.duan@intel.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.