mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	Jacob Pan <jacob.jun.pan@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	Joerg Roedel <joro@8bytes.org>
Cc: baolu.lu@linux.intel.com, Robin Murphy <robin.murphy@arm.com>,
	Will Deacon <will@kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	"Raj, Ashok" <ashok.raj@intel.com>,
	"Liu, Yi L" <yi.l.liu@intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Ghorai, Sukumar" <sukumar.ghorai@intel.com>
Subject: Re: [PATCH v3] iommu/vt-d: Fix PASID directory pointer coherency
Date: Fri, 21 Apr 2023 10:34:15 +0800	[thread overview]
Message-ID: <706b94c0-b0bd-4488-081f-6a955b99284a@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB52762EABB8EF8E685291604A8C639@BN9PR11MB5276.namprd11.prod.outlook.com>

On 4/20/23 4:16 PM, Tian, Kevin wrote:
>> From: Jacob Pan <jacob.jun.pan@linux.intel.com>
>> Sent: Wednesday, April 5, 2023 11:45 PM
>>
>> On platforms that do not support IOMMU Extended capability bit 0
>> Page-walk Coherency, CPU caches are not snooped when IOMMU is
>> accessing
>> any translation structures. IOMMU access goes only directly to
>> memory. Intel IOMMU code was missing a flush for the PASID table
>> directory that resulted in the unrecoverable fault as shown below.
>>
>> This patch adds clflush calls whenever allocating and updating
>> a PASID table directory to ensure cache coherency.
>>
>> On the reverse direction, there's no need to clflush the PASID directory
>> pointer when we deactivate a context entry in that IOMMU hardware will
>> not see the old PASID directory pointer after we clear the context entry.
>> PASID directory entries are also never freed once allocated.
>>
>> [    0.555386] DMAR: DRHD: handling fault status reg 3
>> [    0.555805] DMAR: [DMA Read NO_PASID] Request device [00:0d.2] fault
>> addr 0x1026a4000 [fault reason 0x51] SM: Present bit in Directory Entry is
>> clear
>> [    0.556348] DMAR: Dump dmar1 table entries for IOVA 0x1026a4000
>> [    0.556348] DMAR: scalable mode root entry: hi 0x0000000102448001, low
>> 0x0000000101b3e001
>> [    0.556348] DMAR: context entry: hi 0x0000000000000000, low
>> 0x0000000101b4d401
>> [    0.556348] DMAR: pasid dir entry: 0x0000000101b4e001
>> [    0.556348] DMAR: pasid table entry[0]: 0x0000000000000109
>> [    0.556348] DMAR: pasid table entry[1]: 0x0000000000000001
>> [    0.556348] DMAR: pasid table entry[2]: 0x0000000000000000
>> [    0.556348] DMAR: pasid table entry[3]: 0x0000000000000000
>> [    0.556348] DMAR: pasid table entry[4]: 0x0000000000000000
>> [    0.556348] DMAR: pasid table entry[5]: 0x0000000000000000
>> [    0.556348] DMAR: pasid table entry[6]: 0x0000000000000000
>> [    0.556348] DMAR: pasid table entry[7]: 0x0000000000000000
>> [    0.556348] DMAR: PTE not present at level 4
>>
>> Cc: <stable@vger.kernel.org>
>> Fixes: 0bbeb01a4faf ("iommu/vt-d: Manage scalalble mode PASID tables")
>> Reported-by: Sukumar Ghorai <sukumar.ghorai@intel.com>
>> Signed-off-by: Ashok Raj <ashok.raj@intel.com>
>> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
>> ---
>> v3: Add clflush after PASID directory allocation to prevent malicious
>> device attack with unauthorized PASIDs. Also flush all the PASID entries
>> after directory updates. (Baolu)
>> v2: Add clflush to PASID directory update case (Baolu, Kevin review)
>> ---
>>   drivers/iommu/intel/iommu.c | 2 ++
>>   drivers/iommu/intel/pasid.c | 7 +++++++
>>   2 files changed, 9 insertions(+)
>>
>> diff --git a/drivers/iommu/intel/iommu.c b/drivers/iommu/intel/iommu.c
>> index 59df7e42fd53..161342e7149d 100644
>> --- a/drivers/iommu/intel/iommu.c
>> +++ b/drivers/iommu/intel/iommu.c
>> @@ -1976,6 +1976,8 @@ static int domain_context_mapping_one(struct
>> dmar_domain *domain,
>>   		pds = context_get_sm_pds(table);
>>   		context->lo = (u64)virt_to_phys(table->table) |
>>   				context_pdts(pds);
>> +		if (!ecap_coherent(iommu->ecap))
>> +			clflush_cache_range(table->table, sizeof(u64));
> 
> v2 of this patch was already merged w/o this change.

The merged patch is v4.

https://lore.kernel.org/all/20230209212843.1788125-1-jacob.jun.pan@linux.intel.com/

> can you elaborate the purpose of v3? Here no flush is required as long
> as it's done in other two places below.

No above code in the merged patch.

Best regards,
baolu

> 
>>
>>   		/* Setup the RID_PASID field: */
>>   		context_set_sm_rid2pasid(context, PASID_RID2PASID);
>> diff --git a/drivers/iommu/intel/pasid.c b/drivers/iommu/intel/pasid.c
>> index fb3c7020028d..979f796175b1 100644
>> --- a/drivers/iommu/intel/pasid.c
>> +++ b/drivers/iommu/intel/pasid.c
>> @@ -128,6 +128,9 @@ int intel_pasid_alloc_table(struct device *dev)
>>   	pasid_table->max_pasid = 1 << (order + PAGE_SHIFT + 3);
>>   	info->pasid_table = pasid_table;
>>
>> +	if (!ecap_coherent(info->iommu->ecap))
>> +		clflush_cache_range(pasid_table->table, size);
>> +
>>   	return 0;
>>   }
>>
>> @@ -215,6 +218,10 @@ static struct pasid_entry
>> *intel_pasid_get_entry(struct device *dev, u32 pasid)
>>   			free_pgtable_page(entries);
>>   			goto retry;
>>   		}
>> +		if (!ecap_coherent(info->iommu->ecap)) {
>> +			clflush_cache_range(entries, VTD_PAGE_SIZE);
>> +			clflush_cache_range(&dir[dir_index].val, sizeof(*dir));
>> +		}
>>   	}
>>
>>   	return &entries[index];
>> --
>> 2.25.1
> 

  reply	other threads:[~2023-04-21  2:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 15:44 Jacob Pan
2023-04-20  8:16 ` Tian, Kevin
2023-04-21  2:34   ` Baolu Lu [this message]
2023-04-21  2:39     ` Tian, Kevin
  -- strict thread matches above, loose matches on Subject: below --
2023-02-08 17:19 Jacob Pan
2023-02-09  2:08 ` Tian, Kevin
2023-02-09 17:06   ` Jacob Pan

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=706b94c0-b0bd-4488-081f-6a955b99284a@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=sukumar.ghorai@intel.com \
    --cc=will@kernel.org \
    --cc=yi.l.liu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®