linux-kernel - Re: [PATCH v3 1/2] usb: core: Amend initial authorized

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <465b2b4d-3c6e-4a64-b3be-f146cb237bda@vaisala.com>
Date: Fri, 9 Feb 2024 16:31:56 +0200
From: Niko Mauno <niko.mauno@...sala.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
 vesa.jaaskelainen@...sala.com, geert@...ux-m68k.org
Subject: Re: [PATCH v3 1/2] usb: core: Amend initial authorized_default value

On 9.2.2024 15.34, Greg KH wrote:
> On Fri, Feb 09, 2024 at 02:39:01PM +0200, Niko Mauno wrote:
>> On 9.2.2024 12.47, Greg KH wrote:
>>> On Fri, Feb 09, 2024 at 11:46:50AM +0200, niko.mauno@...sala.com wrote:
>>>> From: Niko Mauno <niko.mauno@...sala.com>
>>>>
>>>> Since the wireless USB implementation has been removed and since the
>>>> behavior with authorized_default values -1 and 1 is now effectively
>>>> same, change the initial value to latter in order to stop using the
>>>> leftover value. The former value can still be passed as a module
>>>> parameter to retain backwards compatibility.
>>>>
>>>> Signed-off-by: Niko Mauno <niko.mauno@...sala.com>
>>>> ---
>>>>    drivers/usb/core/hcd.c | 6 ++----
>>>>    1 file changed, 2 insertions(+), 4 deletions(-)
>>>
>>> Isn't this series already in my tree?
>>>
>>> confused,
>>>
>>> greg k-h
>>
>> Hi Greg, apologies for any confusion I may have caused,
>>
>> Geert requested some further clarification in the new Kconfig help section,
>> please see:
>> https://marc.info/?l=linux-usb&m=170747246528305&w=2
> 
> Great, but I can't take patches that are already in my tree, right?
> 
> Please submit a new one on top of what I currently have.
> 
>> (There shouldn't be any functional change introduced between v2 and v3)
> 
> That always needs to be listed, as my bot says, otherwise we have no
> idea what is going on here.  Remember, some of us get 1000+ emails a day
> to do something with (review, apply, delete, ignore...)
> 
> thanks,
> 
> greg k-h

Thanks, submitted as new patch against usb-next.
-Niko