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
Subject: [PATCH v2 0/3] Handle notifications on overlayfs fake path files
Date: Sun, 11 Jun 2023 16:27:29 +0300 [thread overview]
Message-ID: <20230611132732.1502040-1-amir73il@gmail.com> (raw)
Miklos,
The first solution that we discussed for removing FMODE_NONOTIFY
from overlayfs real files using file_fake container got complicated.
This alternative solution is less intrusive to vfs and all the vfs
code should remian unaffected expect for the special fsnotify case
that we want to fix.
Thanks,
Amir.
Changes since v1:
- Drop the file_fake container
- Leave f_path fake and special case only fsnotify
[1] https://github.com/amir73il/linux/commits/ovl_real_path
Amir Goldstein (3):
fs: rename FMODE_NOACCOUNT to FMODE_INTERNAL
fs: introduce f_real_path() helper
ovl: enable fsnotify events on underlying real files
Documentation/filesystems/locking.rst | 3 ++-
Documentation/filesystems/vfs.rst | 3 ++-
fs/file_table.c | 29 ++++++++++++++++++++++++---
fs/internal.h | 5 +++--
fs/namei.c | 2 +-
fs/open.c | 2 +-
fs/overlayfs/file.c | 4 ++--
fs/overlayfs/super.c | 27 ++++++++++++++++---------
include/linux/dcache.h | 11 ++++++----
include/linux/fs.h | 8 +++++---
include/linux/fsnotify.h | 6 ++++--
11 files changed, 71 insertions(+), 29 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-11 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 13:27 Amir Goldstein [this message]
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
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=20230611132732.1502040-1-amir73il@gmail.com \
--to=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).