linux-kernel - Re: [PATCH] USB: serial: option: set driver

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] [day] [month] [year] [list]

Message-ID: <87r2b27pl5.fsf@miraculix.mork.no>
Date:   Tue, 19 Mar 2019 18:15:34 +0100
From:   Bjørn Mork <bjorn@...k.no>
To:     Måns Rullgård <mans@...sr.com>
Cc:     Dan Williams <dcbw@...hat.com>, Johan Hovold <johan@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: serial: option: set driver_info for SIM5218 and compatibles

Måns Rullgård <mans@...sr.com> writes:

> Every time you think USB can't get any worse, it does.

You can't blame vendor creativity on the bus spec.  Look at what the
same vendors do to e.g. SCSI to make these firmwares appear as different
USB devices.  The fact that some of then use "eject" as a signal to
reboot the firmware into some other mode is not a SCSI problem.

But I do agree that USB should have dropped "vendor specific" and
mandated class functions for everything.  In theory. In practice, that
would probably have casued USB to lose to some other competing spec with
vendor specific as an option...

Bjørn