net: thunderbolt: Unregister ThunderboltIP protocol handler when suspending
authorMika Westerberg <mika.westerberg@linux.intel.com>
Fri, 28 Sep 2018 09:21:17 +0000 (12:21 +0300)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 15 Jun 2019 09:54:07 +0000 (11:54 +0200)
commit47e6a354e24881c89e936393459ae39a98c4c9de
tree5be9dd3487ef4a995b3573d100db3d0dd73e5bb9
parent31aa2a7a8566fac337d976d9da62d12cfafa8611
net: thunderbolt: Unregister ThunderboltIP protocol handler when suspending

[ Upstream commit 9872760eb7b1d4f6066ad8b560714a5d0a728fdb ]

The XDomain protocol messages may start as soon as Thunderbolt control
channel is started. This means that if the other host starts sending
ThunderboltIP packets early enough they will be passed to the network
driver which then gets confused because its resume hook is not called
yet.

Fix this by unregistering the ThunderboltIP protocol handler when
suspending and registering it back on resume.

Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Acked-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
drivers/net/thunderbolt.c