linux-kernel - Re: Linux v5.5 serious PCI bug

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: <PSXP216MB043809A423446A6EF2C7909A80580@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
Date:   Mon, 9 Dec 2019 13:33:49 +0000
From:   Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>
To:     "mika.westerberg@...ux.intel.com" <mika.westerberg@...ux.intel.com>
CC:     Bjorn Helgaas <helgaas@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: Linux v5.5 serious PCI bug

On Mon, Dec 09, 2019 at 03:12:39PM +0200, mika.westerberg@...ux.intel.com wrote:
> On Mon, Dec 09, 2019 at 12:34:04PM +0000, Nicholas Johnson wrote:
> > Hi,
> > 
> > I have compiled Linux v5.5-rc1 and thought all was good until I 
> > hot-removed a Gigabyte Aorus eGPU from Thunderbolt. The driver for the 
> > GPU was not loaded (blacklisted) so the crash is nothing to do with the 
> > GPU driver.
> > 
> > We had:
> > - kernel NULL pointer dereference
> > - refcount_t: underflow; use-after-free.
> > 
> > Attaching dmesg for now; will bisect and come back with results.
> 
> Looks like something related to iommu. Does it work if you disable it?
> (intel_iommu=off in the command line).
On Mon, Dec 09, 2019 at 03:12:39PM +0200, mika.westerberg@...ux.intel.com wrote:
> On Mon, Dec 09, 2019 at 12:34:04PM +0000, Nicholas Johnson wrote:
> > Hi,
> > 
> > I have compiled Linux v5.5-rc1 and thought all was good until I 
> > hot-removed a Gigabyte Aorus eGPU from Thunderbolt. The driver for the 
> > GPU was not loaded (blacklisted) so the crash is nothing to do with the 
> > GPU driver.
> > 
> > We had:
> > - kernel NULL pointer dereference
> > - refcount_t: underflow; use-after-free.
> > 
> > Attaching dmesg for now; will bisect and come back with results.
> 
> Looks like something related to iommu. Does it work if you disable it?
> (intel_iommu=off in the command line).
I thought it could be that, too.

The attachment "dmesg-4" from the original email is with iommu parameters.
The attachment "dmesg-5" from the original email is with no iommu parameters.
Attaching here "dmesg-6" with the iommu explicitly set off like you said.

No difference, still broken. Although, with iommu off, there are less stack traces.

Could it be sysfs-related?

Kind regards,
Nicholas

View attachment "dmesg-6" of type "text/plain" (112026 bytes)