netdev - Re: [PATCH 01/28] net: thunderbolt: Unregister ThunderboltIP protocol handler when suspending

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: <20190129.101024.2142969510882311385.davem@davemloft.net>
Date:   Tue, 29 Jan 2019 10:10:24 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     mika.westerberg@...ux.intel.com
Cc:     linux-kernel@...r.kernel.org, michael.jamet@...el.com,
        YehezkelShB@...il.com, andreas.noever@...il.com, lukas@...ner.de,
        andriy.shevchenko@...ux.intel.com, netdev@...r.kernel.org
Subject: Re: [PATCH 01/28] net: thunderbolt: Unregister ThunderboltIP
 protocol handler when suspending

From: Mika Westerberg <mika.westerberg@...ux.intel.com>
Date: Tue, 29 Jan 2019 18:01:16 +0300

> 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@...ux.intel.com>

Acked-by: David S. Miller <davem@...emloft.net>