linux-kernel - Re: 答复: 答复: 答复: [PATCH] iommu/vt-d: Don't reject nvme host due to scope mismatch

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]

Date:   Tue, 24 Dec 2019 19:26:53 +0800
From:   Lu Baolu <baolu.lu@...ux.intel.com>
To:     "Jim,Yan" <jimyan@...du.com>,
        Jerry Snitselaar <jsnitsel@...hat.com>
Cc:     "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 答复: 答复: 答复: [PATCH] iommu/vt-d: Don't reject nvme host due to scope mismatch

Hi,

On 2019/12/24 16:18, Jim,Yan wrote:
>>>> For both cases, a quirk flag seems to be more reasonable, so that
>>>> unrelated devices will not be impacted.
>>>>
>>>> Best regards,
>>>> baolu
>>> Hi Baolu,
>>> 	Thanks for your advice. And I modify the patch as follow.
>> I just posted a patch for both NTG and NVME cases. Can you please take a look?
>> Does it work for you?
>>
>> Best regards,
>> baolu
>>
> I have tested your patch. It does work for me. But I prefer my second version, it is more flexible, and may use for similar unknown devices.
> 

I didn't get your point. Do you mind explaining why it's more flexible?

Best regards,
baolu