> ... buggering the filesystems (and boxen) that never planned to use > that garbage. > I'm planning to rework this as dentry ops again. Your other comments point out some issues that also exist in the old dentry_operations, so that's a good opportunity to fix those up. How do you feel about just having the two entries in struct super_block? With them there, I can add the dentry_operations to fs/unicode where they won't bother anyone else, while not making every filesystem that uses it have to carry near identical code. > > Are you serious? > 1) who said that ->d_inode is stable here? If we are in RCU mode, > it won't be. > 2) page-sized kmalloc/kfree *ON* *COMPONENT* *AFTER* *COMPONENT*? > #2 is the part that made me the saddest in the patch. I'm planning to move this to the unicode subsystem so it can just walk through the name as it computes the hash without needing any allocation. > > ... and again, you are pulling in a lot of cachelines. > I probably should've just given it a DCACHE flag, like what fscrypt is using. A simple flag there would've done everything that I'm doing without making the cache super sad and making any attempts at making it actually work with RCU much simpler. > <understatement> IMO the whole thing is not a good idea. </understatement>
