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: <20230104145032.GA1069244@bhelgaas>
Date:   Wed, 4 Jan 2023 08:50:32 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     "Liang, Kan" <kan.liang@...ux.intel.com>
Cc:     bhelgaas@...gle.com, hdegoede@...hat.com, kernelorg@...ead.fr,
        kjhambrick@...il.com, 2lprbe78@...k.com,
        nicholas.johnson-opensource@...look.com.au, benoitg@...us.ca,
        mika.westerberg@...ux.intel.com, wse@...edocomputers.com,
        mumblingdrunkard@...tonmail.com, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org, david.e.box@...el.com,
        yunying.sun@...el.com
Subject: Re: Bug report: the extended PCI config space is missed with 6.2-rc2

On Wed, Jan 04, 2023 at 09:39:56AM -0500, Liang, Kan wrote:
> Hi Bjorn,
> 
> Happy new year!
> 
> We found some PCI issues with the latest 6.2-rc2.
> 
> - Using the lspci -xxxx, the extended PCI config space of all PCI
> devices are missed with the latest 6.2-rc2. The system we used had 932
> PCI devices, at least 800 which have extended space as seen when booted
> into a 5.15 kernel. But none of them appeared in 6.2-rc2.
> - The drivers which rely on the information in the extended PCI config
> space don't work anymore. We have confirmed that the perf uncore driver
> (uncore performance monitoring) and Intel VSEC driver (telemetry) don't
> work in 6.2-rc2. There could be more drivers which are impacted.
> 
> After a bisect, we found the regression is caused by the below commit
> 07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map").
> After reverting the commit, the issues are gone.
> 
> Could you please take a look at the issues?

Certainly.  Can you capture the complete dmesg log, please?

Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ