stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Sanjay Kumar <sanjay.k.kumar@intel.com>,
	stable@vger.kernel.org, Jon Derrick <jonathan.derrick@intel.com>
Subject: Re: [PATCH 06/19] iommu/vt-d: Fix clearing real DMA device's scalable-mode context entries
Date: Fri, 6 May 2022 16:52:49 +0200	[thread overview]
Message-ID: <YnU2QcC7QQzvcWUI@kroah.com> (raw)
In-Reply-To: <20220506120057.77320-6-llfl@linux.alibaba.com>

On Fri, May 06, 2022 at 08:00:44PM +0800, Kun(llfl) wrote:
> From: Lu Baolu <baolu.lu@linux.intel.com>
> 
> ANBZ: #1105
> 
> commit 474dd1c6506411752a9b2f2233eec11f1733a099 upstream.
> 
> The commit 2b0140c69637e ("iommu/vt-d: Use pci_real_dma_dev() for mapping")
> fixes an issue of "sub-device is removed where the context entry is cleared
> for all aliases". But this commit didn't consider the PASID entry and PASID
> table in VT-d scalable mode. This fix increases the coverage of scalable
> mode.
> 
> Suggested-by: Sanjay Kumar <sanjay.k.kumar@intel.com>
> Fixes: 8038bdb855331 ("iommu/vt-d: Only clear real DMA device's context entries")
> Fixes: 2b0140c69637e ("iommu/vt-d: Use pci_real_dma_dev() for mapping")
> Cc: stable@vger.kernel.org # v5.6+

Same here, what kernels is this to be applied to, and what is the "ANBZ"
tag?

thanks,

greg k-h

      reply	other threads:[~2022-05-06 14:53 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
     [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 [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=YnU2QcC7QQzvcWUI@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=jiangbo.wu@intel.com \
    --cc=jonathan.derrick@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).