From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
Dmytro Maluka <dmaluka@chromium.org>,
Samiullah Khawaja <skhawaja@google.com>,
Kevin Tian <kevin.tian@intel.com>,
Joerg Roedel <joerg.roedel@amd.com>,
David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Keshavamurthy, Anil S" <anil.s.keshavamurthy@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Adrian Bunk <bunk@stusta.de>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Konstantin Andreev <andreev@swemel.ru>
Subject: Re: [PATCH 6.12.y] iommu/vt-d: Clear Present bit before tearing down context entry
Date: Thu, 16 Jul 2026 21:37:32 -0400 [thread overview]
Message-ID: <20260716232340.0005-stable-reply@kernel.org> (raw)
In-Reply-To: <20260714222124.1906678-1-andreev@swemel.ru>
On Wed, Jul 15, 2026 at 01:21:23AM +0300, Konstantin Andreev wrote:
> When tearing down a context entry, the current implementation zeros the
> entire 128-bit entry using multiple 64-bit writes. This creates a window
> where the hardware can fetch a "torn" entry — where some fields are
> already zeroed while the 'Present' bit is still set — leading to
> unpredictable behavior or spurious faults.
Queued for 6.12, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-17 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 22:21 [PATCH 6.12.y] iommu/vt-d: Clear Present bit before tearing down context entry Konstantin Andreev
2026-07-17 1:37 ` 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=20260716232340.0005-stable-reply@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreev@swemel.ru \
--cc=anil.s.keshavamurthy@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=bunk@stusta.de \
--cc=dmaluka@chromium.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=skhawaja@google.com \
--cc=stable@vger.kernel.org \
--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