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  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:	Sat, 16 Dec 2006 09:05:32 +0000
From:	Pavel Machek <>
To:	Linus Torvalds <>
Cc:	"Michael K. Edwards" <>,
	Greg KH <>, Andrew Morton <>,
Subject: Re: [GIT PATCH] more Driver core patches for 2.6.19


> > Seriously, though, please please pretty please do not allow a facility
> > for "going through a simple interface to get accesses to irqs and
> > memory regions" into the mainline kernel, with or without toy ISA
> > examples.
> I do agree.
> I'm not violently opposed to something like this in practice (we've 
> already allowed it for USB devices), but there definitely needs to be a 
> real reason that helps _us_, not just some ass-hat vendor that looks for a 
> way to avoid open-sourcing their driver.
> If there are real and valid uses (and as mentioned, I actually think that 
> the whole graphics-3D-engine-thing is such a use) where a kernel driver 
> simply doesn't work out well, or where there are serious tecnical reasons 
> why it wants to be in user space (and "stability" is not one such thing: 
> if you access hardware directly in user space, and your driver is buggy, 
> the machine is equally deal, and a hell of a lot harder to control to 
> boot).

Well.. it is easier to debug in userspace. While bad hw access can
still kill the box, bad free() will not, and most bugs in early
developent are actually of 2nd kind.
Thanks for all the (sleeping) penguins.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists