netdev - when to cancel kevents in usbnet

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>] [day] [month] [year] [list]

Message-ID: <18f621e2-93dd-4153-8c37-f219deb4206d@suse.com>
Date: Thu, 28 Aug 2025 15:53:26 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Bjørn Mork <bjorn@...k.no>,
 Alan Stern <stern@...land.harvard.edu>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
 USB list <linux-usb@...r.kernel.org>
Subject: when to cancel kevents in usbnet

Hi,

I am looking at how kevents are handled. However, recent fiascos
I am reluctant to touch this area. Nevertheless, right now we are
cancelling all deferred kevents upon stop() being called.
It seems to me that that is correct with one exception.
If the deferred kevent is the need to clear a halt, we cannot
just drop that. The only reason we should do so is disconnect().
What do you think? Does this need to be split?

	Regards
		Oliver