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: <E1JlO90-0005gJ-MH@pomaz-ex.szeredi.hu>
Date:	Mon, 14 Apr 2008 14:50:46 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	dwmw2@...radead.org
CC:	miklos@...redi.hu, 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,

Sure, but that needs reviewer time, tester time and developer time.
All of those is limited, and for a piece of code with <100 users and
>1kloc it may not be worth it.

But if people do it for fun, or for having a simple example code to
look at, I have no problem with that :)

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