Classroom.<\/p>\n
\nWrapfs is a full-fledged stackable null-layer (or loopback)\nfilesystem that simply passes all operations and objects\n(unmodified) between the VFS and the lower filesystem. Wrapfs\nitself, however, is not easy to write for one main reason; it has\nto treat the lower filesystem as if it were the VFS, while\nappearing to the real Linux VFS as a lower-level filesystem. This\ndual role requires careful handling of locks, reference counts,\nallocated memory and so on. Luckily, someone already wrote and\nmaintains Wrapfs. Therefore, Wrapfs serves as an excellent template\nfor you to modify and add new functionality.\n\nsource : http:\/\/www.linuxjournal.com\/article\/6485\n<\/pre>\n<\/p>\n
Get The Hang <\/u><\/h4>\n
\nint wrapfs_unlink(struct inode *dir,\n struct dentry *dentry)\n{\n int err = 0;\n struct inode *lower_dir;\n struct dentry *lower_dentry;\n lower_dir = get_lower_inode(dir);\n lower_dentry = get_lower_dentry(dentry);\n \/* pre-call code can go here *\/\n err = lower_dir->i_op->unlink(lower_dir,\n lower_dentry);\n \/* post-call code can go here *\/\n return err;\n}\n\nsource : http:\/\/www.linuxjournal.com\/article\/6485\n<\/pre>\n","protected":false},"excerpt":{"rendered":"Classroom. Wrapfs is a full-fledged stackable null-layer (or loopback) filesystem that simply passes all operations and objects (unmodified) between the VFS and the lower filesystem. Wrapfs itself, however, is not easy to write for one main reason; it has to treat the lower filesystem as if it were the VFS, while appearing to the real … <\/p>\n