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: <YgzTsLV/nSKp7FWP@kroah.com>
Date:   Wed, 16 Feb 2022 11:36:32 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     3090101217@....edu.cn
Cc:     balbi@...nel.org, ruslan.bilovol@...il.com,
        pavel.hofman@...tera.com, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org, Jing Leng <jleng@...arella.com>
Subject: Re: [PATCH] usb: gadget: f_uac1: add set requests support

On Wed, Feb 16, 2022 at 05:43:01PM +0800, 3090101217@....edu.cn wrote:
> From: Jing Leng <jleng@...arella.com>
> 
> Currently the f_uac1 driver only supports UAC_SET_CUR request.
> 
> But when uac1 device is plugged to Ubuntu 20.04 PC, at the stage
> of setup, the PC will send UAC_SET_RES request, If the device
> doesn't respond to the request, the PC will abort the setup process
> and uac1 device can't be recognized on Ubuntu 20.04 PC.

So is this a bug in the Host side to not do stuff like this?  Why not
fix it there instead?

Where is the requirement that this command must be handled by the
device?

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ