linux-kernel - Stack trace when removing Thunderbolt devices while kernel shutting down

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]

Message-ID: <PSXP216MB0438220243C0097569D4B2DB80110@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
Date:   Tue, 18 Feb 2020 14:18:40 +0000
From:   Nicholas Johnson <nicholas.johnson-opensource@...look.com.au>
To:     Bjorn Helgaas <helgaas@...nel.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Stack trace when removing Thunderbolt devices while kernel shutting
 down

Hi Bjorn,

If I surprise remove Thunderbolt 3 devices just as the kernel is 
shutting down, I get stack dumps, when those devices would not normally 
cause stack dumps if the kernel were not shutting down.

Because the kernel is shutting down, it makes it difficult to capture 
the logs without a serial console.

In your mind, is this cause for concern? There is no harm caused and the 
kernel still shuts down. The main thing I am worried about is if this 
means that the locking around the subsystem is not strict enough.

If you think this is worth looking into, I will try to learn about how 
the native interrupts are handled and try to investigate, and I will 
also try to get my serial console working again to capture the details.

Thank you for any thoughts you may give.

Kind regards,
Nicholas Johnson.