linux-kernel - RE: [PATCH] USB: Fix configuration selection issues introduced in v4.20.0

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: <C672AA6DAAC36042A98BAD0B0B25BDA94CB2885A@BGSMSX104.gar.corp.intel.com>
Date:   Thu, 17 Jan 2019 03:53:45 +0000
From:   "Gopal, Saranya" <saranya.gopal@...el.com>
To:     Nikolay Yakimov <root@...id.pp.ru>
CC:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] USB: Fix configuration selection issues introduced in
 v4.20.0

> The result is this:
> Before f13912d3f014a, if an RNDIS device has non-vendor-specific
> configurations after the first one, that one would be selected.
> After ff2a8c532c14, the first configuration would always be selected
> for RNDIS devices. Besides, there are several redundant checks in this
> case, which is, if nothing else, confusing.
> 
> Hopefully I've explained my point clearly enough.

Agreed. Thanks for pointing it out. I somehow missed this :(

Thanks,
Saranya