From: Al Viro <viro@zeniv.linux.org.uk>
To: Chengguang Xu <cgxu519@mykernel.net>
Cc: miklos@szeredi.hu, amir73il@gmail.com, jack@suse.cz,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] fs: introduce notifier list for vfs inode
Date: Thu, 15 Oct 2020 04:25:01 +0100 [thread overview]
Message-ID: <20201015032501.GO3576660@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20201010142355.741645-2-cgxu519@mykernel.net>
On Sat, Oct 10, 2020 at 10:23:51PM +0800, Chengguang Xu wrote:
> Currently there is no notification api for kernel about modification
> of vfs inode, in some use cases like overlayfs, this kind of notification
> will be very helpful to implement containerized syncfs functionality.
> As the first attempt, we introduce marking inode dirty notification so that
> overlay's inode could mark itself dirty as well and then only sync dirty
> overlay inode while syncfs.
Who's responsible for removing the crap from notifier chain? And how does
that affect the lifetime of inode?
next prev parent reply other threads:[~2020-10-15 3:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 14:23 [RFC PATCH 0/5] implement containerized syncfs for overlayfs Chengguang Xu
2020-10-10 14:23 ` [RFC PATCH 1/5] fs: introduce notifier list for vfs inode Chengguang Xu
2020-10-14 16:15 ` Jan Kara
2020-10-15 3:03 ` Chengguang Xu
2020-10-15 6:11 ` Amir Goldstein
2020-10-15 11:29 ` Chengguang Xu
2020-10-15 12:32 ` Amir Goldstein
2020-10-15 13:13 ` Chengguang Xu
2020-10-15 16:02 ` Amir Goldstein
2020-10-15 16:06 ` Amir Goldstein
2020-10-16 1:56 ` Chengguang Xu
2020-10-16 4:39 ` Amir Goldstein
2020-10-16 7:43 ` Chengguang Xu
2020-10-15 3:25 ` Al Viro [this message]
2020-10-15 3:42 ` Chengguang Xu
2020-10-15 4:57 ` Al Viro
2020-10-15 10:56 ` Chengguang Xu
2020-10-16 7:09 ` Chengguang Xu
2020-10-16 9:22 ` Jan Kara
2020-10-10 14:23 ` [RFC PATCH 2/5] fs: export symbol of writeback_single_inode() Chengguang Xu
2020-10-10 14:23 ` [RFC PATCH 3/5] ovl: setup overlayfs' private bdi Chengguang Xu
2020-10-10 14:23 ` [RFC PATCH 4/5] ovl: monitor marking dirty activity of underlying upper inode Chengguang Xu
2020-10-11 1:16 ` kernel test robot
2020-10-11 1:55 ` kernel test robot
2020-10-10 14:23 ` [RFC PATCH 5/5] ovl: impement containerized syncfs for overlayfs Chengguang Xu
2020-10-11 2:57 ` kernel test robot
2020-10-11 3:10 ` kernel test robot
2020-10-11 13:08 ` kernel test robot
2020-10-12 12:31 ` Dan Carpenter
2020-10-12 12:31 ` Dan Carpenter
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=20201015032501.GO3576660@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=cgxu519@mykernel.net \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.