From: Greg KH <gregkh@linuxfoundation.org>
To: "Kun(llfl)" <llfl@linux.alibaba.com>
Cc: Jiangbo Wu <jiangbo.wu@intel.com>, Xu Yu <xuyu@linux.alibaba.com>,
Sanjay Kumar <sanjay.k.kumar@intel.com>,
stable@vger.kernel.org, Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH 05/19] iommu/vt-d: Global devTLB flush when present context entry changed
Date: Fri, 6 May 2022 16:52:18 +0200 [thread overview]
Message-ID: <YnU2Is7w6u6TZK9V@kroah.com> (raw)
In-Reply-To: <20220506120057.77320-5-llfl@linux.alibaba.com>
On Fri, May 06, 2022 at 08:00:43PM +0800, Kun(llfl) wrote:
> From: Sanjay Kumar <sanjay.k.kumar@intel.com>
>
> ANBZ: #1105
What is this?
> commit 37764b952e1b39053defc7ebe5dcd8c4e3e78de9 upstream.
>
> This fixes a bug in context cache clear operation. The code was not
> following the correct invalidation flow. A global device TLB invalidation
> should be added after the IOTLB invalidation. At the same time, it
> uses the domain ID from the context entry. But in scalable mode, the
> domain ID is in PASID table entry, not context entry.
>
> Fixes: 7373a8cc38197 ("iommu/vt-d: Setup context and enable RID2PASID support")
> Cc: stable@vger.kernel.org # v5.0+
Is this a 5.10 backport for us to pick up? What about 5.4?
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-06 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220506120057.77320-1-llfl@linux.alibaba.com>
2022-05-06 12:00 ` [PATCH 05/19] iommu/vt-d: Global devTLB flush when present context entry changed Kun(llfl)
2022-05-06 14:52 ` Greg KH [this message]
[not found] ` <2fa72980-d94f-3257-1ea4-5ff9c77f8b59@linux.alibaba.com>
2022-05-07 11:29 ` Greg KH
2022-05-06 12:00 ` [PATCH 06/19] iommu/vt-d: Fix clearing real DMA device's scalable-mode context entries Kun(llfl)
2022-05-06 14:52 ` Greg KH
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=YnU2Is7w6u6TZK9V@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=baolu.lu@linux.intel.com \
--cc=jiangbo.wu@intel.com \
--cc=llfl@linux.alibaba.com \
--cc=sanjay.k.kumar@intel.com \
--cc=stable@vger.kernel.org \
--cc=xuyu@linux.alibaba.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.