linux-kernel - Re: VFS design question

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: <464F3CB2.9060401@zytor.com>
Date:	Sat, 19 May 2007 11:06:42 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Tobias Pflug <tobias.pflug@....net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: VFS design question

Tobias Pflug wrote:
> Hi,
> 
> A note in front: I realize that my question is rather broad and a bit
> vague, sorry for that :)
> 
> The VFS is a great solution to transparently operate on different file
> systems by designating an interface for file systems that separates 
> file system specific code from higher levels. 
> 
> Doesn't however this very feature also represent a limiting factor in
> some way? Surely you can map pretty much anything to the Common File
> System model, but is or has the VFS interface design been limiting
> in any way in contemporary file system design ? 
> 

Why does this sound like "do my homework for me"?

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