linux-kernel - [PATCH 0/1] RFC: Make thunderbolt NHI driver work with kexec

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: <20200520181240.118559-1-mlevitsk@redhat.com>
Date:   Wed, 20 May 2020 21:12:39 +0300
From:   Maxim Levitsky <mlevitsk@...hat.com>
To:     kvm@...r.kernel.org
Cc:     Michael Jamet <michael.jamet@...el.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Andreas Noever <andreas.noever@...il.com>,
        linux-usb@...r.kernel.org (open list:THUNDERBOLT DRIVER),
        Yehezkel Bernat <YehezkelShB@...il.com>,
        linux-kernel@...r.kernel.org (open list),
        Jiri Kosina <trivial@...nel.org>,
        Maxim Levitsky <mlevitsk@...hat.com>
Subject: [PATCH 0/1] RFC: Make thunderbolt NHI driver work with kexec

While trying to use kexec on my desktop,
which has Titan Ridge Thunderbolt add-on card,
I noticed that after a kexec, system hangs
for about a minute in the 'wating for udev devices
to settle' phase of the boot.

I found out that if I unload the thunderbolt driver
prior to the kexec, then it works just fine.

Looking at the code I see that the driver doeesn't
implement .shutdown method, so this on-liner patch
points it to the same method that is used on device removal.

I don't know if this is the right solution,
but it does appear to work just fine with this patch.

What do you think?

Best regards,
	Maxim Levitsky

Maxim Levitsky (1):
  thunderbolt: add trivial .shutdown

 drivers/thunderbolt/nhi.c | 1 +
 1 file changed, 1 insertion(+)

-- 
2.25.4