linux-kernel - Re: [PATCH] USB: serial: fix stringify operator in usb-serial-simple

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: <20130818194005.GA19107@kroah.com>
Date:	Sun, 18 Aug 2013 12:40:05 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Yann Droneaud <yann@...neaud.fr>
Cc:	Yann Droneaud <ydroneaud@...eya.com>,
	Wei Shuai <cpuwolf@...il.com>,
	Frans Klaver <frans.klaver@...ns.com>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: serial: fix stringify operator in usb-serial-simple

On Sun, Aug 18, 2013 at 09:29:00PM +0200, Yann Droneaud wrote:
> From: Yann Droneaud <ydroneaud@...eya.com>
> 
> usb-serial-simple uses an unknown stringify macro that make
> all drivers being named "stringify(vendor)".
> 
> This can be a problem when two drivers have the same (wrong) name:
> 
>     kernel: usbcore: registered new interface driver usb_serial_simple
>     kernel: usbserial: USB Serial support registered for stringify(vendor)
>     kernel Error: Driver 'stringify(vendor)' is already registered, aborting...
>     kernel: usbserial: problem -16 when registering driver stringify(vendor)
>     kernel: usbserial: USB Serial deregistering driver stringify(vendor)
>     kernel: usbcore: deregistering interface driver usb_serial_simple
> 

Ugh, sorry about that, I thought there used to be a stringify() macro
that used to do this.  Nice patch, I'll queue it up.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/