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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 24 Feb 2012 10:19:36 -0500
From:	Jidong Xiao <jidong.xiao@...il.com>
To:	Kernel development list <linux-kernel@...r.kernel.org>
Cc:	Greg KH <greg@...ah.com>
Subject: Re: Can we move device drivers into user-space?

On Wed, Feb 22, 2012 at 11:56 PM, Jidong Xiao <jidong.xiao@...il.com> wrote:
> Hi,
>
> I am just curious. Since the concept user-space device drivers has
> been proposed for several years, and some related projects and
> research papers have demonstrated the feasibility of of moving device
> drivers into use space. In particular, this paper:
>
> Tolerating Malicious Device Drivers in Linux.
> http://pdos.csail.mit.edu/papers/sud:usenix10.pdf
>
> In this paper, existing device driver code need not to be changed,
> which should help the idea to be applied in practice.
>
> The advantage and disadvantage of move device drivers into use space
> of both obvious:
>
> Advantage: Since most of kernel bugs are caused by device drivers
> issues, moving device drivers into user space can reduce the impact of
> device driver bugs. From security perspective, the system can be more
> secure and robust if most device drivers are working in user space.
> Disadvantage: At least, existing techniques as well as the above paper
> showed a relatively high overhead.
>
> So is it mainly because the high overhead that prevents the user-space
> device drivers ideas being accepted in Linux?
>

Actually, my major concern is, since UIO has been accepted, then why
don't we move all the rest device drivers into user space as well. As
I understand, currently, some of device drivers are running on user
space, while the other (or say the majority of) device drivers are
running on kernel space, so why don't we maintain a consistent device
drivers infrastructure, say, either all in user space, or all in
kernel space. (Sure some critical device drivers still need to be kept
in kernel space.)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ