From: Kundan Kumar <kundan.kumar@samsung.com>
To: jaegeuk@kernel.org, chao@kernel.org, agruenba@redhat.com,
trondmy@kernel.org, anna@kernel.org, hch@lst.de,
brauner@kernel.org, jack@suse.cz, viro@zeniv.linux.org.uk,
djwong@kernel.org, jlayton@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, gfs2@lists.linux.dev,
linux-nfs@vger.kernel.org, gost.dev@samsung.com,
anuj20.g@samsung.com, vishak.g@samsung.com, joshi.k@samsung.com,
Kundan Kumar <kundan.kumar@samsung.com>
Subject: [PATCH v2 0/4] Avoid filesystem references to writeback internals
Date: Fri, 13 Feb 2026 11:16:30 +0530 [thread overview]
Message-ID: <20260213054634.79785-1-kundan.kumar@samsung.com> (raw)
In-Reply-To: CGME20260213055123epcas5p25f52d5961c04b1a1f514827a494a0773@epcas5p2.samsung.com
The series introduces writeback helper APIs and converts f2fs, gfs2
and nfs to stop accessing writeback internals directly.
As suggested by Christoph [1], filesystem code that directly accesses
writeback internals is split out:
[1] https://lore.kernel.org/all/20251015072912.GA11294@lst.de/
No functional changes intended.
Changes since v1:
1) Added comment indicating that these functions shall not be used by
filesystems that support cgroup writeback. (Christoph)
2) Pass inode instead of bdi for modifying writeback accounting stats,
will make it easier to select proper wb context for the upcoming
parallel writeback patches. (hence dropped the previous reviewed-bys
for patch 4)
Kundan Kumar (4):
writeback: prep helpers for dirty-limit and writeback accounting
f2fs: stop using writeback internals for dirty_exceeded checks
gfs2: stop using writeback internals for dirty_exceeded check
nfs: stop using writeback internals for WB_WRITEBACK accounting
fs/f2fs/node.c | 4 ++--
fs/f2fs/segment.h | 2 +-
fs/gfs2/super.c | 2 +-
fs/nfs/internal.h | 2 +-
fs/nfs/write.c | 3 +--
include/linux/backing-dev.h | 13 +++++++++++++
6 files changed, 19 insertions(+), 7 deletions(-)
base-commit: 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b
--
2.25.1
next parent reply other threads:[~2026-02-13 5:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260213055123epcas5p25f52d5961c04b1a1f514827a494a0773@epcas5p2.samsung.com>
2026-02-13 5:46 ` Kundan Kumar [this message]
2026-02-13 5:46 ` [PATCH v2 1/4] writeback: prep helpers for dirty-limit and writeback accounting Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 2/4] f2fs: stop using writeback internals for dirty_exceeded checks Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 3/4] gfs2: stop using writeback internals for dirty_exceeded check Kundan Kumar
2026-02-13 5:46 ` [PATCH v2 4/4] nfs: stop using writeback internals for WB_WRITEBACK accounting Kundan Kumar
2026-02-13 6:24 ` [PATCH v2 0/4] Avoid filesystem references to writeback internals Christoph Hellwig
2026-02-17 12:26 ` Christian Brauner
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=20260213054634.79785-1-kundan.kumar@samsung.com \
--to=kundan.kumar@samsung.com \
--cc=agruenba@redhat.com \
--cc=anna@kernel.org \
--cc=anuj20.g@samsung.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=gfs2@lists.linux.dev \
--cc=gost.dev@samsung.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jlayton@kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vishak.g@samsung.com \
/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