linux-kernel - Re: [PATCH] USB Elan FTDI: check for workqueue creation v2

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: <20070224164448.8fe872c7.zaitcev@redhat.com>
Date:	Sat, 24 Feb 2007 16:44:48 -0800
From:	Pete Zaitcev <zaitcev@...hat.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	linux-kernel-list <linux-kernel@...r.kernel.org>,
	<tony.olech@...ndigitalsystems.com>,
	linux-usb-devel@...ts.sourceforge.net
Subject: Re: [PATCH] USB Elan FTDI: check for workqueue creation v2

On Sat, 24 Feb 2007 10:41:15 +0300, Cyrill Gorcunov <gorcunov@...il.com> wrote:

> Thanks a lot for comments and Ack the patch please.

Cyrill, I forgot to mention a couple of points, sorry.

>          printk(KERN_INFO "driver %s built at %s on %s\n", ftdi_elan_driver.name,
> -                 __TIME__, __DATE__);
> +	       __TIME__, __DATE__);

Is this really necessary?

>          respond_queue = create_singlethread_workqueue("ftdi-respond-engine");
> +	if (!respond_queue)
> +		goto err3;

This is good, but...

>          result = usb_register(&ftdi_elan_driver);
>          if (result)
>                  printk(KERN_ERR "usb_register failed. Error number %d\n",
> -                        result);
> +		       result);
>          return result;

What does happen if usb_register fails? Since you fixed the
create_singlethread_workqueue, why not this too?

-- Pete
cc: to Tony@...N and linux-usb-devel
-
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/