On Fri, Apr 30, 2021 at 03:17:02AM +0000, Justin He wrote: > Is it a good idea to introduce a new d_path_nolock() for file_dentry_name()? > In d_path_nolock(), if it detects that there is conflicts with mount_lock > or rename_lock, then returned NULL as a name of that vfsmount? Just what does vfsmount have to do with rename_lock? And what's the point of the entire mess, anyway?
