From: Jeff Layton <jlayton@kernel.org>
To: Kundan Kumar <kundan.kumar@samsung.com>,
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, pankaj.raghav@linux.dev
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,
mcgrof@kernel.org
Subject: Re: [PATCH 0/4] Avoid filesystem references to writeback internals
Date: Wed, 11 Feb 2026 08:30:22 -0500 [thread overview]
Message-ID: <c830a8afe51514ac40fa272558eed4fcbb5efcea.camel@kernel.org> (raw)
In-Reply-To: <20260211070057.22001-1-kundan.kumar@samsung.com>
On Wed, 2026-02-11 at 12:30 +0530, Kundan Kumar wrote:
> 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
>
> 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 | 4 ++--
> include/linux/backing-dev.h | 11 +++++++++++
> 6 files changed, 18 insertions(+), 7 deletions(-)
>
>
> base-commit: 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b
Seems sensible.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-02-11 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260211070533epcas5p32f50f317b20250bb61b1b5a0b3a2a5d9@epcas5p3.samsung.com>
2026-02-11 7:00 ` [PATCH 0/4] Avoid filesystem references to writeback internals Kundan Kumar
2026-02-11 7:00 ` [PATCH 1/4] writeback: prep helpers for dirty-limit and writeback accounting Kundan Kumar
2026-02-11 10:39 ` Jan Kara
2026-02-11 7:00 ` [PATCH 2/4] f2fs: stop using writeback internals for dirty_exceeded checks Kundan Kumar
2026-02-11 7:00 ` [PATCH 3/4] gfs2: stop using writeback internals for dirty_exceeded check Kundan Kumar
2026-02-11 7:00 ` [PATCH 4/4] nfs: stop using writeback internals for WB_WRITEBACK accounting Kundan Kumar
2026-02-11 13:30 ` Jeff Layton [this message]
2026-02-11 13:49 ` [PATCH 0/4] Avoid filesystem references to writeback internals Andreas Gruenbacher
2026-02-11 15:53 ` Christoph Hellwig
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=c830a8afe51514ac40fa272558eed4fcbb5efcea.camel@kernel.org \
--to=jlayton@kernel.org \
--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=joshi.k@samsung.com \
--cc=kundan.kumar@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=pankaj.raghav@linux.dev \
--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