linux-kernel - Re: [GIT PATCH] more Driver core patches for 2.6.19

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:	Wed, 13 Dec 2006 13:03:27 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	"Michael K. Edwards" <medwards.linux@...il.com>
cc:	Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PATCH] more Driver core patches for 2.6.19

On Wed, 13 Dec 2006, Michael K. Edwards wrote:
>
> On 12/13/06, Linus Torvalds <torvalds@...l.org> wrote:
> > Ok, what kind of ass-hat idiotic thing is this?
> 
> C'mon, Linus, tell us how you _really_ feel.

I'll try to be less subtle next time ;)

> 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).

Microkernel people have their heads up their arses, none of their 
arguments have actually ever made any real logical sense. So look 
elsewhere for real reasons to do it in user space.

		Linus
-
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/