linux-kernel - Re: [PATCH] usb: add quirks for Lenovo OneLink+ Dock

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: <31aeee3c-f4f1-16a8-272b-96da5d4a565e@suse.com>
Date:   Tue, 30 Aug 2022 13:54:43 +0200
From:   Oliver Neukum <oneukum@...e.com>
To:     JFLF <jflf_kernel@....com>, gregkh@...uxfoundation.org,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: add quirks for Lenovo OneLink+ Dock

On 24.08.22 18:09, JFLF wrote:

> By process of elimination the controllers themselves were identified as
> the cause of the problem. Through trial and error the issue was solved
> by using USB_QUIRK_RESET_RESUME for both chips.

Hi,

aside from the aspects of getting this properly signed off and merged,
this opens up a question. What does resetting a hub do to its children?
That is if the request to wake up comes from a child, do we

a) lose state in the child?
b) retain the knowledge which port requested the wakeup?

How far has this patch been tested?

	Regards
		Oliver