| 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
| ||
|
Date: Sat, 19 May 2007 23:51:56 +0200 From: Tobias Pflug <tobias.pflug@....net> To: "H. Peter Anvin" <hpa@...or.com> Cc: linux-kernel@...r.kernel.org Subject: Re: VFS design question On Sat, 2007-05-19 at 11:06 -0700, H. Peter Anvin wrote: > 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 I tried to make it clear that I am clearly lacking expertise in this topic. I am currently working on a somewhat related topic and was hoping to get some reactions that would point me in the right directions as it is somewhat hard to judge the VFS design when you do not have prior experience in writing a file system on your own. Nowhere did I ask for a 10 paged review on the matter. Enough blablabla Any input would be welcome. Thanks. -Tobi - 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