From: Christoph Hellwig <hch@lst.de>
To: Kundan Kumar <kundan.kumar@samsung.com>
Cc: 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,
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 16:53:46 +0100 [thread overview]
Message-ID: <20260211155346.GA10445@lst.de> (raw)
In-Reply-To: <20260211070057.22001-1-kundan.kumar@samsung.com>
Looks fine as a cleanup, but maybe add comments that these functions
must not be used by file systems that support cgroup writeback and
thus can have multiple bdi_writeback structures per bdi?
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Kundan Kumar <kundan.kumar@samsung.com>
Cc: brauner@kernel.org, jack@suse.cz, agruenba@redhat.com,
pankaj.raghav@linux.dev, djwong@kernel.org, anuj20.g@samsung.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, gfs2@lists.linux.dev,
mcgrof@kernel.org, viro@zeniv.linux.org.uk, anna@kernel.org,
gost.dev@samsung.com, jaegeuk@kernel.org, vishak.g@samsung.com,
linux-nfs@vger.kernel.org, hch@lst.de, trondmy@kernel.org
Subject: Re: [f2fs-dev] [PATCH 0/4] Avoid filesystem references to writeback internals
Date: Wed, 11 Feb 2026 16:53:46 +0100 [thread overview]
Message-ID: <20260211155346.GA10445@lst.de> (raw)
In-Reply-To: <20260211070057.22001-1-kundan.kumar@samsung.com>
Looks fine as a cleanup, but maybe add comments that these functions
must not be used by file systems that support cgroup writeback and
thus can have multiple bdi_writeback structures per bdi?
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-02-11 15:53 UTC|newest]
Thread overview: 18+ 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 ` [f2fs-dev] " Kundan Kumar
2026-02-11 7:00 ` [PATCH 1/4] writeback: prep helpers for dirty-limit and writeback accounting Kundan Kumar
2026-02-11 7:00 ` [f2fs-dev] " Kundan Kumar
2026-02-11 10:39 ` Jan Kara
2026-02-11 10:39 ` [f2fs-dev] " 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 ` [f2fs-dev] " 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 ` [f2fs-dev] " Kundan Kumar
2026-02-11 7:00 ` [PATCH 4/4] nfs: stop using writeback internals for WB_WRITEBACK accounting Kundan Kumar
2026-02-11 7:00 ` [f2fs-dev] " Kundan Kumar
2026-02-11 13:30 ` [PATCH 0/4] Avoid filesystem references to writeback internals Jeff Layton
2026-02-11 13:30 ` [f2fs-dev] " Jeff Layton via Linux-f2fs-devel
2026-02-11 13:49 ` Andreas Gruenbacher
2026-02-11 13:49 ` [f2fs-dev] " Andreas Gruenbacher via Linux-f2fs-devel
2026-02-11 15:53 ` Christoph Hellwig [this message]
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=20260211155346.GA10445@lst.de \
--to=hch@lst.de \
--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=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 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.