linux-kernel - Re: Can we move device drivers into user-space?

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:	Fri, 24 Feb 2012 20:15:35 +0100
From:	"Henrik Rydberg" <rydberg@...omail.se>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Guenter Roeck <guenter.roeck@...csson.com>,
	Jidong Xiao <jidong.xiao@...il.com>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Can we move device drivers into user-space?

> > Given the choice, I would be quite happy to piss off some robots. Call
> > it a prejudice if you like ;).
> 
> You can't control how people use an interface.  You will note that there
> are no stupid users of the UIO interface in the kernel today, we can't
> control what people do in the privacy of their own companies/homes,
> despite numerous governments trying to do so in the past.
> 
> So yes, people will always do stupid, foolish things.  And they were
> doing them before UIO came along, now they just have the chance to at
> least do those foolish things in a way that interfaces with the kernel
> in a semi-sane manner, not messing anything else in the kernel up.

So the question is; can the uio example be repeated in other areas, to
bring more kernel power to userspace?

No doubt, the kernel has fostered an unprecedented code-quality view,
which, IMHO, is the bottom line. As long as that quality remains
unchallenged, having all drivers in-kernel will remain the best
choice. But, suppose some entity managed to keep that quality in
userspace, would there be any reason to think of it as a bad idea? I
think not.

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