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: <25981cc9-243e-bece-4e85-86f3c880d96f@linux.intel.com>
Date:   Tue, 22 Nov 2022 17:41:19 +0800
From:   Baolu Lu <baolu.lu@...ux.intel.com>
To:     Joerg Roedel <joro@...tes.org>
Cc:     baolu.lu@...ux.intel.com, iommu@...ts.linux.dev,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] [PULL REQUEST] Intel IOMMU updates for Linux v6.2

Hi Joerg,

On 2022/11/22 17:06, Joerg Roedel wrote:
> Hi Baolu,
> 
> On Tue, Nov 22, 2022 at 08:29:42AM +0800, Lu Baolu wrote:
>> Lu Baolu (7):
>>    iommu/vt-d: Allocate pasid table in device probe path
>>    iommu/vt-d: Add device_block_translation() helper
>>    iommu/vt-d: Add blocking domain support
>>    iommu/vt-d: Rename iommu_disable_dev_iotlb()
>>    iommu/vt-d: Rename domain_add_dev_info()
>>    iommu/vt-d: Remove unnecessary domain_context_mapped()
>>    iommu/vt-d: Use real field for indication of first level
> 
> Applied the first 6 patches. The last one has conflicts and doesn't
> apply on top of my x86/vt-d branch. Could you please have a look please?

I guess the last patch conflicts with below commit:

242b0aaeabbe ("iommu/vt-d: Preset Access bit for IOVA in FL non-leaf 
paging entries")

which was merged in v6.1-rc6. Can you please bring the x86/vt-d branch
to v6.1-rc6, or do you want me to rebase that patch on the existing top
of the branch?

Best regards,
baolu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ