linux-kernel - Re: [PATCH 0/7] OMFS filesystem version 3

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]

Message-Id: <1208171143.31695.54.camel@pmac.infradead.org>
Date:	Mon, 14 Apr 2008 12:05:43 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	jamie@...reable.org, hch@...radead.org, akpm@...ux-foundation.org,
	me@...copeland.com, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/7] OMFS filesystem version 3

On Mon, 2008-04-14 at 11:58 +0200, Miklos Szeredi wrote:
> Oh, you mean without having to run the whole kernel around the
> filesystem?  Well, that's a bit more tricky: filesystems use not just
> the VFS API, but the block, VM, SLAB, etc. APIs as well.  Porting all
> of these to userspace and keeping them in sync with the kernel changes
> doesn't sound much fun.

That would be UML :)

But seriously -- wouldn't our time be better spent on improving error
handling in the kernel, rather than taking advantage of the benefits of
microkernel design... but only for those parts which don't matter?

-- 
dwmw2

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