linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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]

Date:	Tue, 12 Feb 2008 15:26:23 -0800
From:	Greg KH <greg@...ah.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, viro@...IV.linux.org.uk,
	torvalds@...ux-foundation.org,
	James.Bottomley@...senPartnership.com, jeff@...zik.org,
	davem@...emloft.net, arjan@...radead.org, sfr@...b.auug.org.au,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

On Tue, Feb 12, 2008 at 10:59:00PM +0000, Alan Cox wrote:
> On Tue, 12 Feb 2008 14:55:31 -0800
> Greg KH <greg@...ah.com> wrote:
> 
> > On Tue, Feb 12, 2008 at 10:20:44PM +0000, Alan Cox wrote:
> > > > I think the best way to get the serial drivers maintained would be to cat
> > > > them all onto the end of synclink.c and hope that Paul thinks he did it.
> > > 
> > > Well I've already broken the buffering so he'd fix it ;)
> > > 
> > > We have a pile of old ISA drivers that are going to break soon with the
> > > locking changes and a pile of USB drivers that when I looked at the
> > > locking were so terminally broken I couldn't be bothered to fix them.
> > 
> > Let me know which USB ones are broken, I'll work to fix them.
> 
> That I noticed doing an audit for unlocking the mctrl functions:
> 
> ir-usb: global variables without locking used in per port operations
> iuu_phoenix: no locking on internal data structures
> mos7840: ditto
> option: ditto
> kobil_sct: ditto
> 
> These drivers do interesting things (where interesting is probably not too
> evil on a PC - except ir-usb) involving playing with data structures
> without locks. It seems there was some kind of evolution along the way as
> some drivers do have a carefully used port private data structure lock
> (or two) but many do not.

Ok, I'll look into them this week.  I'm currently working on revamping
the option driver as it had the mistake of being based on the keyspan
drivers, which weren't the nicest to start with...

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/