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: <20230105175105.GA1155450@bhelgaas>
Date:   Thu, 5 Jan 2023 11:51:05 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Tony Luck <tony.luck@...el.com>
Cc:     "Liang, Kan" <kan.liang@...ux.intel.com>, 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 Thu, Jan 05, 2023 at 09:42:10AM -0800, Tony Luck wrote:
> On Wed, Jan 04, 2023 at 09:45:11AM -0600, Bjorn Helgaas wrote:
> > My understanding is that EfiMemoryMappedIO tells the OS to map the
> > area for use by runtime services, but is not intended to prevent the
> > OS from using the area.  Some platforms use EfiMemoryMappedIO for PCI
> > host bridge apertures, and of course the OS needs to use those.
> > 
> > If your firmware folks disagree and think Linux should be able to
> > figure this out differently, I would love to have a conversation about
> > how to do this.
> 
> It seems that 07eab0901ede ("efi/x86: Remove EfiMemoryMappedIO from E820 map")
> is also the cause of breakage for drivers/edac/sb_edac.c. It is broken
> in v6.2-rc2 and reverting this commit makes it work again.
> 
> This ancient driver probably plays fast and loose with how it ought to
> access extended PCIe config space ... but it needs to do this to read various
> memory controller configuration registers to do address translation from
> a system physical address to a DIMM address.

Hi Tony, can you share a dmesg log?  Does it look like the same thing
Kan reported, where the ECAM space is reported only via an
EfiMemoryMappedIO region and is not otherwise reserved by firmware?

Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ