linux-kernel - Re: [PATCH rc 1/8] iommu/vt-d: Track nested domains in parent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ba25e0b1-fd7f-4813-924d-b116a88dbb5d@intel.com>
Date: Thu, 8 Feb 2024 17:23:06 +0800
From: Yi Liu <yi.l.liu@...el.com>
To: "Tian, Kevin" <kevin.tian@...el.com>, "joro@...tes.org" <joro@...tes.org>,
	"jgg@...dia.com" <jgg@...dia.com>, "baolu.lu@...ux.intel.com"
	<baolu.lu@...ux.intel.com>
CC: "alex.williamson@...hat.com" <alex.williamson@...hat.com>,
	"robin.murphy@....com" <robin.murphy@....com>, "eric.auger@...hat.com"
	<eric.auger@...hat.com>, "nicolinc@...dia.com" <nicolinc@...dia.com>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "chao.p.peng@...ux.intel.com"
	<chao.p.peng@...ux.intel.com>, "yi.y.sun@...ux.intel.com"
	<yi.y.sun@...ux.intel.com>, "iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>, "Duan,
 Zhenzhong" <zhenzhong.duan@...el.com>, "joao.m.martins@...cle.com"
	<joao.m.martins@...cle.com>
Subject: Re: [PATCH rc 1/8] iommu/vt-d: Track nested domains in parent



On 2024/2/8 16:28, Tian, Kevin wrote:
>> From: Liu, Yi L <yi.l.liu@...el.com>
>> Sent: Thursday, February 8, 2024 4:23 PM
>>
>>   static void intel_nested_domain_free(struct iommu_domain *domain)
>>   {
>> +	struct dmar_domain *dmar_domain = to_dmar_domain(domain);
>> +	struct dmar_domain *s2_domain = dmar_domain->s2_domain;
>> +
>> +	spin_lock(&s2_domain->s1_lock);
>> +	list_del(&dmar_domain->s2_link);
>> +	spin_unlock(&s2_domain->s1_lock);
>>   	kfree(to_dmar_domain(domain));
> 
> use 'dmar_domain'.

Oops. yes it is.

> Reviewed-by: Kevin Tian <kevin.tian@...el.com>

-- 
Regards,
Yi Liu