Hi, Is it necessary for every filesystem supported by kernel 2.6 to have a implementation of alloc_inode vfs ops ? The reason i am asking this is because earlier in 2.4 days we had fs specific inode info structure embedded in the inode structure in a union, which means that even if you allocate new inode via a call to new_inode, the inode returned had enough space allocated to hold your data, while in 2.6 this is replaced by just a pointer i_private. So if you use kernel to allocate a new inode, you only have space to hold a pointer and not enough fs data. Any comments/suggestions ?? I hope I am able to explain my problem properly. this is a link to the same question i asked previously on the list. http://article.gmane.org/gmane.linux.kernel.kernelnewbies/24116 -- Thanks & Regards, ******************************************** Manish Katiyar ( http://mkatiyar.googlepages.com ) 3rd Floor, Fair Winds Block EGL Software Park Off Intermediate Ring Road Bangalore 560071, India *********************************************** -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
