linux-kernel - Re: [PATCH v2] usb: gadget: legacy gadgets are optional

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: <CAGkQfmMPRNs7wHA9Wp0EC6gV=Zh_oRXwEyuJ2jdHvO16Pv1owA@mail.gmail.com>
Date:   Fri, 10 Mar 2017 10:39:49 +0100
From:   Romain Izard <romain.izard.pro@...il.com>
To:     Felipe Balbi <balbi@...nel.org>
Cc:     linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "# 4 . 9+" <stable@...r.kernel.org>
Subject: Re: [PATCH v2] usb: gadget: legacy gadgets are optional

Hello Felipe,

2017-03-10 10:15 GMT+01:00 Felipe Balbi <balbi@...nel.org>:
>
> Hi,
>
> Romain Izard <romain.izard.pro@...il.com> writes:
>> With commit "usb: gadget: don't couple configfs to legacy gadgets"
>> it is possible to build a modular kernel with both built-in configfs
>> support and modular legacy gadget drivers.
>>
>> But when building a kernel without modules, it is also necessary to be
>> able to build with configfs but without any legacy gadget driver.
>>
>> Mark the choice for legacy gadget drivers as optional.
>>
>> Fixes: bc49d1d17dcf ("usb: gadget: don't couple configfs to legacy gadgets")
>> Cc: <stable@...r.kernel.org> # 4.9+
>
> this is *NOT* a fix since this requirement didn't exist before.

It worked in 4.1, as a non-modular kernel would only have a single entry
from the USB gadget driver choice option, and USB_CONFIGFS was one of
those.

When I moved on to 4.9, this configuration could not be selected anymore.

>
>> Signed-off-by: Romain Izard <romain.izard.pro@...il.com>
>> ---
>> changes in v2:
>>  - Reword description
>>
>>  drivers/usb/gadget/Kconfig | 11 +++++++++--
>>  1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/usb/gadget/Kconfig b/drivers/usb/gadget/Kconfig
>> index 8ad203296079..e157e9aa4f3d 100644
>> --- a/drivers/usb/gadget/Kconfig
>> +++ b/drivers/usb/gadget/Kconfig
>> @@ -212,7 +212,7 @@ config USB_F_TCM
>>  # this first set of drivers all depend on bulk-capable hardware.
>>
>>  config USB_CONFIGFS
>> -     tristate "USB functions configurable through configfs"
>> +     tristate "USB Gadget functions configurable through configfs"
>
> unrelated change
>
>>       select USB_LIBCOMPOSITE
>>       help
>>         A Linux USB "gadget" can be set up through configfs.
>> @@ -458,8 +458,9 @@ config USB_CONFIGFS_F_TCM
>>         UAS utilizes the USB 3.0 feature called streams support.
>>
>>  choice
>> -     tristate "USB Gadget Drivers"
>> +     tristate "USB Gadget precomposed configurations"
>
> unrelated change
>
>>       default USB_ETH
>> +     optional
>>       help
>>         A Linux "Gadget Driver" talks to the USB Peripheral Controller
>>         driver through the abstract "gadget" API.  Some other operating
>> @@ -476,6 +477,12 @@ choice
>>         not be able work with that controller, or might need to implement
>>         a less common variant of a device class protocol.
>>
>> +       The available choices each represent a single precomposed USB
>> +       gadget configuration. In the device model, each option contains
>> +       both the device instanciation as a child for a USB gadget
>> +       controller, and the relevant drivers for each function declared
>> +       by the device.
>
> unrelated change

I'll split this.

Best regards,
-- 
Romain Izard