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] [day] [month] [year] [list]
Date:   Mon, 5 Dec 2022 08:29:48 -0800
From:   Jacob Pan <jacob.jun.pan@...ux.intel.com>
To:     Ashok Raj <ashok.raj@...el.com>
Cc:     <iommu@...ts.linux.dev>, LKML <linux-kernel@...r.kernel.org>,
        Lu Baolu <baolu.lu@...ux.intel.com>,
        Joerg Roedel <joro@...tes.org>,
        David Woodhouse <dwmw2@...radead.org>,
        Robin Murphy <robin.murphy@....com>,
        Will Deacon <will@...nel.org>, Yi Liu <yi.l.liu@...el.com>,
        "Tian, Kevin" <kevin.tian@...el.com>,
        Raghunathan Srinivasan <raghunathan.srinivasan@...el.com>,
        jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH] iommu/vt-d: Fix buggy QAT device mask

Hi Ashok,

On Fri, 2 Dec 2022 17:41:19 -0800, Ashok Raj <ashok.raj@...el.com> wrote:

> On Fri, Dec 02, 2022 at 04:56:10PM -0800, Jacob Pan wrote:
> > Impacted QAT device IDs that need extra dtlb flush quirk is ranging
> > from 0x4940 to 0x4943. After bitwise AND device ID with 0xfffc the
> > result should be 0x4940 instead of 0x494c to identify these devices.  
> 
> Can you add the lore link for the original post here just for reference.
> 
> as a Link: tag, since this depends on the other patch.
yes, Looks like Baolu  has already taken care of it.

Thank you both!

Jacob

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ