linux-kernel - Re: [PATCH next] usb: usbfs: Add reset

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: <dd3583a1-e66d-46e5-aba8-61ffb268f9a7@suse.com>
Date: Wed, 17 Jul 2024 17:27:51 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Alan Stern <stern@...land.harvard.edu>, Hongyu Xie <xy521521@...il.com>
Cc: oneukum@...e.com, gregkh@...uxfoundation.org, brauner@...nel.org,
 jlayton@...nel.org, jack@...e.cz, linux-usb@...r.kernel.org,
 linux-kernel@...r.kernel.org, xiehongyu1@...inos.cn
Subject: Re: [PATCH next] usb: usbfs: Add reset_resume for usbfs

On 17.07.24 15:44, Alan Stern wrote:
> On Wed, Jul 17, 2024 at 11:13:39AM +0800, Hongyu Xie wrote:
>> From: Hongyu Xie <xiehongyu1@...inos.cn>
>>
>>
>>
>> On 2024/7/17 10:05, Alan Stern wrote:

> 
> That's right, it should be possible to avoid rebinding.  But we can't do
> this until we have some way to tell the userspace driver that a reset
> has occurred.  Oliver's idea is to do this by returning a special error
> code for the next ioctl, and I can't think of anything better.

I wish you could, for this is supremely inelegant. In particular
it forces user space to reinit the device when it is needed, instead
of when it is idle.

Yet, I think conceptually the first ioctl absolutely must fail,
because the device state has been lost.

	Regards
		Oliver