lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 30 Apr 2021 03:21:28 +0000 From: Al Viro <viro@...iv.linux.org.uk> To: Justin He <Justin.He@....com> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Rasmus Villemoes <linux@...musvillemoes.dk>, Christoph Hellwig <hch@....de>, "Darrick J. Wong" <djwong@...nel.org>, linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-xfs <linux-xfs@...r.kernel.org>, Dave Chinner <david@...morbit.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Eric Sandeen <sandeen@...deen.net>, Andy Shevchenko <andy.shevchenko@...il.com> Subject: Re: [GIT PULL] iomap: new code for 5.13-rc1 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?
Powered by blists - more mailing lists