On Tue, May 03, 2016 at 10:04:03PM +0200, Miklos Szeredi wrote: > Hi Al, > git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next > > This fixes two issues with overlayfs. > > Thanks, > Miklos > > --- > Miklos Szeredi (3): > vfs: rename: check backing inode being equal > vfs: export lookup_hash() to modules > ovl: ignore permissions on underlying lookup NAK on lookup_hash(). If nothing else, you need either lookup_one_len_unlocked() or its "we already know hash" variant (assuming it's worth bothering with). That locking the parent is potentially a lot costlier than recalculating the (default) hash function. Especially in -next, where lookup_one_len_unlocked() will take the lock shared if it has to take it at all, but the mainline one also has a good chance to avoid taking the lock. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
