From: Josef Bacik <josef@toxicpanda.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
Amir Goldstein <amir73il@gmail.com>,
Christian Brauner <brauner@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Chris Mason <mason@kernel.org>,
Chengguang Xu <cgxu519@mykernel.net>,
linux-unionfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Chengguang Xu <charliecgxu@tencent.com>,
Josef Bacik <josef@toxicpanda.com>
Subject: [PATCH v3 2/8] ovl: setup overlayfs' private bdi
Date: Wed, 04 Nov 2026 20:44:59 +0000 [thread overview]
Message-ID: <20261104-b4-ovl-containerized-sync-v3-2-8daa20144f53@toxicpanda.com> (raw)
In-Reply-To: <20261104-b4-ovl-containerized-sync-v3-0-8daa20144f53@toxicpanda.com>
From: Chengguang Xu <charliecgxu@tencent.com>
Setup overlayfs' private bdi so that we can collect
overlayfs' own dirty inodes.
Signed-off-by: Chengguang Xu <charliecgxu@tencent.com>
[josef: only for an overlay that tracks dirty inodes, add
ovl_tracks_dirty()]
Signed-off-by: Josef Bacik <josef@toxicpanda.com>
---
fs/overlayfs/overlayfs.h | 18 ++++++++++++++++++
fs/overlayfs/super.c | 10 ++++++++++
2 files changed, 28 insertions(+)
diff --git a/fs/overlayfs/overlayfs.h b/fs/overlayfs/overlayfs.h
index 444e28c09145..0ef81c7a9701 100644
--- a/fs/overlayfs/overlayfs.h
+++ b/fs/overlayfs/overlayfs.h
@@ -7,6 +7,7 @@
#include <linux/kernel.h>
#include <linux/uuid.h>
#include <linux/fs.h>
+#include <linux/backing-dev.h>
#include <linux/fsverity.h>
#include <linux/namei.h>
#include <linux/posix_acl.h>
@@ -683,6 +684,23 @@ static inline bool ovl_should_sync_upper_fs(struct ovl_fs *ofs)
ofs->config.fsync_mode == OVL_FSYNC_STRICT;
}
+/*
+ * Does this overlay track the upper inodes that are modified through it, so
+ * that syncfs() and unmount only have to sync those?
+ *
+ * Only with fsync=relaxed. In the other modes the overlay never syncs, or it
+ * syncs the entire upper filesystem. fsync=auto does not count until it has
+ * been resolved. sync_filesystem() does not write any inodes of a filesystem
+ * that has no writeback, like tmpfs, and nothing ever clears their dirty flags.
+ */
+static inline bool ovl_tracks_dirty(struct ovl_fs *ofs)
+{
+ if (!ovl_upper_mnt(ofs) || ofs->config.fsync_mode != OVL_FSYNC_RELAXED)
+ return false;
+
+ return ovl_upper_mnt(ofs)->mnt_sb->s_bdi != &noop_backing_dev_info;
+}
+
/*
* To avoid regressions in existing setups with overlay lower offline changes,
* we allow lower changes only if none of the new features are used.
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index 4500038d6941..efa4d862039c 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -1479,6 +1479,16 @@ static int ovl_fill_super_creds(struct fs_context *fc, struct super_block *sb)
if (!ofs->workdir)
sb->s_flags |= SB_RDONLY;
+ /*
+ * Dirty overlay inodes go on the lists of this bdi.
+ * ovl_get_workdir() has resolved fsync=auto.
+ */
+ if (ovl_tracks_dirty(ofs)) {
+ err = super_setup_bdi(sb);
+ if (err)
+ return err;
+ }
+
sb->s_stack_depth = upper_sb->s_stack_depth;
sb->s_time_gran = upper_sb->s_time_gran;
}
--
2.55.0
next prev parent reply other threads:[~2026-11-04 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 20:44 [PATCH v3 0/8] ovl: only sync what was written through the overlay Josef Bacik
2026-11-04 20:44 ` [PATCH v3 1/8] ovl: expand fsync mount options Josef Bacik
2026-11-04 20:44 ` Josef Bacik [this message]
2026-11-04 20:45 ` [PATCH v3 3/8] ovl: make the root inode appear hashed Josef Bacik
2026-11-04 20:45 ` [PATCH v3 4/8] ovl: mark the overlay inode dirty on modification Josef Bacik
2026-11-04 20:45 ` [PATCH v3 5/8] ovl: implement overlayfs' own ->write_inode operation Josef Bacik
2026-11-04 20:45 ` [PATCH v3 6/8] ovl: cache dirty overlayfs' inode Josef Bacik
2026-11-04 20:45 ` [PATCH v3 7/8] ovl: handle lazytime on the upper filesystem Josef Bacik
2026-11-04 20:45 ` [PATCH v3 8/8] ovl: implement containerized syncfs for overlayfs Josef Bacik
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=20261104-b4-ovl-containerized-sync-v3-2-8daa20144f53@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=cgxu519@mykernel.net \
--cc=charliecgxu@tencent.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mason@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
all inboxes | Powered by JetHome®