linux-kernel - Oops on 4.15-rc[123] on shutdown/reboot

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-next>] [day] [month] [year] [list]

Date:   Mon, 11 Dec 2017 15:31:19 +0000
From:   Chris Clayton <chris2553@...glemail.com>
To:     LKML <linux-kernel@...r.kernel.org>
Cc:     okaya@...eaurora.org, bhelgaas@...gle.com
Subject: Oops on 4.15-rc[123] on shutdown/reboot

I've been getting an oops when shutting down my laptop (with /sbin/halt) or rebooting it (/sbin/reboot or
/usr/sbin/kexec). Unfortunately, I can't provide the backtrace because it is on the screen for only a moment before the
system shuts down/reboots.

I have however, bisected it and the outcome is:

cc27b735ad3a75574a6ab1a66ed6b09385e77e5e is the first bad commit
commit cc27b735ad3a75574a6ab1a66ed6b09385e77e5e
Author: Sinan Kaya <okaya@...eaurora.org>
Date:   Wed Oct 25 15:01:02 2017 -0400

    PCI/portdrv: Turn off PCIe services during shutdown

    Some of the PCIe services such as AER are being left enabled during
    shutdown. This might cause spurious AER errors while SOC is being powered
    down.

    Clean up the PCIe services gracefully during shutdown to clear these false
    positives.

    Signed-off-by: Sinan Kaya <okaya@...eaurora.org>
    Signed-off-by: Bjorn Helgaas <bhelgaas@...gle.com>

:040000 040000 5a827d6956c581344a0bf392e30155c337673c1d 76c6a39b53604a0a0a370383c3503f80aa7cbc1e M	drivers

I'm confident that this is the correct outcome because a kernel built with the preceding commit
(6018182d3158505f11103adaee8ffb53424df986) does not oops. Nor does -rc3 with the patch reversed.

I'm more than happy to provide additional diagnostics and test proposed fixes. As a starter for ten, I've attached the
output from 'lspci -v'. If, however, you need to see the backtrace, I'll need some advice on how to capture that.

Chris

View attachment "lspci-v.txt" of type "text/plain" (10653 bytes)