From: Al Viro <viro@zeniv.linux.org.uk>
To: Justin He <Justin.He@arm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Sandeen <sandeen@sandeen.net>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [GIT PULL] iomap: new code for 5.13-rc1
Date: Fri, 30 Apr 2021 03:21:28 +0000 [thread overview]
Message-ID: <YIt3uKBQnlxHAo/Q@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <AM6PR08MB43769965CAF732F1DEA4A37AF75E9@AM6PR08MB4376.eurprd08.prod.outlook.com>
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?
next prev parent reply other threads:[~2021-04-30 3:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 2:58 [GIT PULL] iomap: new code for 5.13-rc1 Darrick J. Wong
2021-04-27 19:40 ` Linus Torvalds
2021-04-27 19:57 ` Christoph Hellwig
2021-04-27 20:05 ` Linus Torvalds
2021-04-28 6:17 ` Christoph Hellwig
2021-04-28 6:38 ` Linus Torvalds
2021-04-28 6:41 ` Christoph Hellwig
2021-04-28 7:14 ` Linus Torvalds
2021-04-28 7:38 ` Rasmus Villemoes
2021-04-28 8:47 ` Justin He
2021-04-28 16:50 ` Linus Torvalds
2021-04-29 6:39 ` Rasmus Villemoes
2021-04-29 16:45 ` Linus Torvalds
2021-04-30 3:17 ` Justin He
2021-04-30 3:21 ` Al Viro [this message]
2021-04-30 6:13 ` Justin He
2021-04-30 18:58 ` Linus Torvalds
2021-04-30 18:50 ` Eric W. Biederman
2021-04-30 19:02 ` Linus Torvalds
2021-04-29 6:43 ` Christoph Hellwig
2021-04-27 20:07 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YIt3uKBQnlxHAo/Q@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Justin.He@arm.com \
--cc=andy.shevchenko@gmail.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sandeen@sandeen.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.