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 23:14:59 +0100
From:	"Henrik Rydberg" <rydberg@...omail.se>
To:	Ted Ts'o <tytso@....edu>, Greg KH <gregkh@...uxfoundation.org>,
	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?

On Fri, Feb 24, 2012 at 04:30:27PM -0500, Ted Ts'o wrote:
> On Fri, Feb 24, 2012 at 10:22:38PM +0100, Henrik Rydberg wrote:
> > 
> > Maintenance. Sure, as soon as an area grows too large for a single
> > person, the current structure will ensure it divides so that the patch
> > stream becomes manageable. We have already seen ample examples of
> > that. But the overall structure of the kernel will become less and
> > less manageable, and the likelihood of duplicates and maintenance
> > problems will increase.
> 
> Not necessarily.  The primary area of growth has been hardware support
> (i.e., drivers), and that scales quite well.
> 
> The main issue is the grown of intra-system interfaces, and you
> haven't shown that this has happened in anything approaching the
> levels where we need to worry.  If we add a new file system, like
> btrfs, that doesn't add a whole new set of VFS interfaces, and it's
> not like we need to worry about communication interfaces between btrfs
> and ext4....

True, and the emergent interface (vfs) is even accessible in
userspace, so all is good in that department for now. Conversely, you
have not shown that this can go on forever. ;-)

The main issue that set me off has been sufficiently diluted in the
(selective) discussion so as to no longer make sense as a reply: At
some point, in-tree or out-of-tree will no longer be distinguishable,
and the question is if/when/why something would/should happen as a
consequence. A matter of politics, if you will. It seemed like an
honest question starting this thread, and I think it is fair to keep
it in mind as such.

Thanks.
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ