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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 19 May 2007 12:14:15 +0200
From:	Tobias Pflug <>
Subject: VFS design question


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 ? 

thanks for your time.

PS: please CC I am not subscribed.thanks

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists