linux-kernel - Re: 答复: [PATCH v1] usb: gadget: uvc: Fixed the abnormal enumeration problem of mobile phone as UVC camera.

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: <2024073132-perjurer-coeditor-40a3@gregkh>
Date: Wed, 31 Jul 2024 11:15:19 +0200
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: 胡连勤 <hulianqin@...o.com>
Cc: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"opensource.kernel" <opensource.kernel@...o.com>
Subject: Re: 答复: [PATCH v1] usb: gadget: uvc: Fixed the abnormal
 enumeration problem of mobile phone as UVC camera.

On Wed, Jul 31, 2024 at 08:46:25AM +0000, 胡连勤 wrote:
> Hello linux community expert:
> 
> The following are answers to several questions about this patch:
> 
> 1.Why does the dwc3 controller matter here?  What about other controllers?
>  We have tested that both the dwc3 controller and the mtu3 controller 
>  have such problems under the uvc function combination.
> 
> 2.Why was this set to be true to start with?  What commit id does this
> fix?  Should it be backported to older kernels, and if so, how far back?
>  Set to true for commit records:
>  https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f277bf27cf5cd56bcd1c4b95ae140f61680a6e83
>  
>  It seems that the f_uvc driver logic is optimized, and the code logic is more reasonable.

Please use the proper "Fixes:" tag on the commit.

>  
>  kernel5.10, kernel 5.15, kernel6.1, and kernel6.6 versions all need to be synchronized, 
>  From the current point of view, these kernel versions will be compatible with Android 14 and newer versions.

So this has never worked at all?  How is that possible?  Others have
used this properly, are you sure nothing is wrong somewhere else?

thanks,

greg k-h