From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: 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,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v3 0/2] Handle notifications on overlayfs fake path files
Date: Mon, 12 Jun 2023 18:18:56 +0300 [thread overview]
Message-ID: <CAOQ4uxhteBXU=3K5CHzgGY30Tiv0qdoVW9d5SFdd1qTn4SBQAA@mail.gmail.com> (raw)
In-Reply-To: <20230611194706.1583818-1-amir73il@gmail.com>
On Sun, Jun 11, 2023 at 10:47 PM Amir Goldstein <amir73il@gmail.com> wrote:
>
> Miklos,
>
> Third attempt with the eye towards simplifying d_real() interface.
>
> Like v2, most of the vfs code should remain unaffected by this
> expect for the special fsnotify case that we wanted to fix.
>
FYI, I've made some changes based on feedback on v3 from
Christoph and Christian:
- Rename struct file_fake to backing_file
- Rename helpers to open_backing_file(), backing_file_real_path()
- Rename FMODE_FAKE_PATH to FMODE_BACKING
- Separate flag from FMODE_NOACCOUNT
- inline the non-backing branch of f_real_path()
Pushed to:
https://github.com/amir73il/linux/commits/ovl_fake_path
Will wait for your feedback before posting v4.
Thanks,
Amir.
>
> Changes since v2:
> - Restore the file_fake container (Miklos)
> - Re-arrange the v1 helpers (Christian)
>
> Changes since v1:
> - Drop the file_fake container
> - Leave f_path fake and special case only fsnotify
>
> Amir Goldstein (2):
> fs: use fake_file container for internal files with fake f_path
> ovl: enable fsnotify events on underlying real files
>
> fs/cachefiles/namei.c | 2 +-
> fs/file_table.c | 91 +++++++++++++++++++++++++++++++++-------
> fs/internal.h | 5 ++-
> fs/namei.c | 16 +++----
> fs/open.c | 28 ++++++++-----
> fs/overlayfs/file.c | 6 +--
> include/linux/fs.h | 15 ++++---
> include/linux/fsnotify.h | 3 +-
> 8 files changed, 121 insertions(+), 45 deletions(-)
>
> --
> 2.34.1
>
prev parent reply other threads:[~2023-06-12 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 19:47 [PATCH v3 0/2] Handle notifications on overlayfs fake path files Amir Goldstein
2023-06-11 19:47 ` [PATCH v3 1/2] fs: use fake_file container for internal files with fake f_path Amir Goldstein
2023-06-12 4:45 ` Christoph Hellwig
2023-06-12 6:37 ` Amir Goldstein
2023-06-12 8:01 ` Christian Brauner
2023-06-12 8:07 ` Christian Brauner
2023-06-12 8:28 ` Amir Goldstein
2023-06-12 8:31 ` Christian Brauner
2023-06-11 19:47 ` [PATCH v3 2/2] ovl: enable fsnotify events on underlying real files Amir Goldstein
2023-06-12 15:18 ` Amir Goldstein [this message]
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='CAOQ4uxhteBXU=3K5CHzgGY30Tiv0qdoVW9d5SFdd1qTn4SBQAA@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=hch@infradead.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).