[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c830a8afe51514ac40fa272558eed4fcbb5efcea.camel@kernel.org>
Date: Wed, 11 Feb 2026 08:30:22 -0500
From: Jeff Layton <jlayton@...nel.org>
To: Kundan Kumar <kundan.kumar@...sung.com>, jaegeuk@...nel.org,
chao@...nel.org, agruenba@...hat.com, trondmy@...nel.org, anna@...nel.org,
hch@....de, brauner@...nel.org, jack@...e.cz, viro@...iv.linux.org.uk,
djwong@...nel.org, pankaj.raghav@...ux.dev
Cc: linux-f2fs-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
gfs2@...ts.linux.dev, linux-nfs@...r.kernel.org, gost.dev@...sung.com,
anuj20.g@...sung.com, vishak.g@...sung.com, joshi.k@...sung.com,
mcgrof@...nel.org
Subject: Re: [PATCH 0/4] Avoid filesystem references to writeback internals
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@...nel.org>
Powered by blists - more mailing lists