From: Christoph Hellwig <hch@infradead.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v2 1/3] fs: rename FMODE_NOACCOUNT to FMODE_INTERNAL
Date: Sun, 11 Jun 2023 23:11:25 -0700 [thread overview]
Message-ID: <ZIa3DfH9D0BIBf8G@infradead.org> (raw)
In-Reply-To: <CAOQ4uxhNtnzpxUzfxjCJ3_7afCG1ye-pHViHjGi8asXTR_Cm3w@mail.gmail.com>
On Mon, Jun 12, 2023 at 09:08:37AM +0300, Amir Goldstein wrote:
> Well, I am not sure if FMODE_FAKE_PATH in v3 is a better name,
> because you did rightfully say that "fake path" is not that descriptive,
> but I will think of a better way to describe "fake path" and match the
> flag to the file container name.
I suspect the just claling it out what it is and naming it
FMODE_OVERLAYFS might be a good idea. We'd just need to make sure not
to set it for the cachefiles use case, which is probably a good idea
anyway.
next prev parent reply other threads:[~2023-06-12 6:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 13:27 [PATCH v2 0/3] Handle notifications on overlayfs fake path files Amir Goldstein
2023-06-11 13:27 ` [PATCH v2 1/3] fs: rename FMODE_NOACCOUNT to FMODE_INTERNAL Amir Goldstein
2023-06-12 4:27 ` Christoph Hellwig
2023-06-12 6:08 ` Amir Goldstein
2023-06-12 6:11 ` Christoph Hellwig [this message]
2023-06-12 6:15 ` Christoph Hellwig
2023-06-12 6:32 ` Amir Goldstein
2023-06-12 6:35 ` Christoph Hellwig
2023-06-11 13:27 ` [PATCH v2 2/3] fs: introduce f_real_path() helper Amir Goldstein
2023-06-12 4:36 ` Christoph Hellwig
2023-06-12 6:28 ` Amir Goldstein
2023-06-12 6:36 ` Christoph Hellwig
2023-06-12 8:13 ` Amir Goldstein
2023-06-11 13:27 ` [PATCH v2 3/3] ovl: enable fsnotify events on underlying real files Amir Goldstein
2023-06-11 14:23 ` [PATCH v2 0/3] Handle notifications on overlayfs fake path files Miklos Szeredi
2023-06-11 16:55 ` Amir Goldstein
2023-06-11 17:52 ` Amir Goldstein
2023-06-11 19:12 ` Miklos Szeredi
2023-06-11 19:25 ` Amir Goldstein
2023-06-11 19:37 ` Miklos Szeredi
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=ZIa3DfH9D0BIBf8G@infradead.org \
--to=hch@infradead.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).