linux-kernel - Re: [PATCH 0/4]: USB: ftdi_sio: fix regression in 2.6.31 and clean up

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: <20091007193329.GA2977@kroah.com>
Date:	Wed, 7 Oct 2009 12:33:29 -0700
From:	Greg KH <greg@...ah.com>
To:	Johan Hovold <jhovold@...il.com>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	Alan Cox <alan@...ux.intel.com>,
	Oliver Neukum <oliver@...kum.org>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4]: USB: ftdi_sio: fix regression in 2.6.31 and clean
 up

On Wed, Oct 07, 2009 at 08:05:03PM +0200, Johan Hovold wrote:
> Hi, 
> 
> These patches clean up the ftdi_sio driver and fixes
> 
>  1) a long outstanding bug manifesting itself as 
>  
>  	BUG: sleeping function called from invalid context at kernel/mutex.c:280
> 
>  2) a couple of regressions in 2.6.31 (stalled reads and unthrottle race)
>     due to changes in the tty layer.
> 
> Please have a look at it so we can get something back-ported to stable as the
> ftdi_sio driver is currently completly broken and unusable due to the stalled
> reads.
> 
> Note that the patches do not add suspend/resume support to the driver (but the
> clean up should make it easier to implement).
> 
> Thanks to Alan Cox, Oliver Neukum, and Alan Stern for all comments and
> suggestions so far.

Very nice, thanks for doing this work, I really appreciate it.  I'll
queue it up as soon as possible.

thanks,

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/