Okay. its already done.
At this point given that we actually have a small user space dependency
and the fact that after I have reviewed the code it looks harmless to
change the inode number of those inodes, in both cases they are just
anonymous inodes generated with new_inode, and anything that we wrap
is likely to be equally so.
So it looks to me like we need to do three things:
- Fix the inode number
I don't see need for doing this for hugetlbfs inodes. Currently, they don't base their
- Fix the name on the hugetlbfs dentry to hold the key
I don't think, the user-space can depend on the dentry-name. It can only depend
- Add a big fat comment that user space programs depend on this
behavior of both the dentry name and the inode number.