netdev - Re: [PATCH v2] r8152: Suspend USB device before shutdown when WoL is enabled

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: <0a706af0-8b19-25c5-1a76-0add28f5d214@suse.com>
Date: Thu, 20 Jul 2023 10:39:36 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Alexandru Gagniuc <alexandru.gagniuc@...com>, linux-usb@...r.kernel.org,
 netdev@...r.kernel.org
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, hayeswang@...ltek.com, jflf_kernel@....com,
 bjorn@...k.no, svenva@...omium.org, linux-kernel@...r.kernel.org,
 eniac-xw.zhang@...com, stable@...r.kernel.org
Subject: Re: [PATCH v2] r8152: Suspend USB device before shutdown when WoL is
 enabled



On 19.07.23 19:37, Alexandru Gagniuc wrote:
> For Wake-on-LAN to work from S5 (shutdown), the USB link must be put
> in U3 state. If it is not, and the host "disappears", the chip will
> no longer respond to WoL triggers.

First, a question, does this also apply to S4?

> To resolve this, add a notifier block and register it as a reboot
> notifier. When WoL is enabled, work through the usb_device struct to
> get to the suspend function. Calling this function puts the link in
> the correct state for WoL to function.

Second, do we really want this to be done for every driver with this issue
or do we want a flag for core USB code to suspend devices when the system
goes down? UAS at least does something similar.

Third, what happens if the device is already suspended when the notifier runs?

	Regards
		Oliver