From: Liz Fong-Jones <lizf@honeycomb.io>
To: Tejun Heo <tj@kernel.org>, Jan Kara <jack@suse.cz>,
Christian Brauner <brauner@kernel.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Xin Yin <yinxin.x@bytedance.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
ian@honeycomb.io
Subject: Re: [PATCH v6 0/3] writeback: let foreign flushes reach dying cgwbs
Date: Tue, 13 Oct 2026 13:34:29 +0000 (UTC) [thread overview]
Message-ID: <20261013133428.725790-1-lizf@honeycomb.io> (raw)
In-Reply-To: <20261002-wb-dying-cgwb-flush-v6-0-1991b4e2dcff@honeycomb.io>
Tejun and Jan,
Gentle ping on v6. Patches 1 and 2 carry Tejun's acks. Patch 3 changed
in v6 to queue replaced_work again when a switch lands on a wb that was
replaced after the switch was queued, as Tejun suggested on v5, and it
hasn't had review yet. Jan, you confirmed on v3 that switching all of a
replaced wb's inodes, dirty ones included, is safe; would you have time
to look at patch 3?
Christian, if they're happy with it, could the series go into
vfs-7.4.misc next to Xin's 168a8c13159c? It still applies cleanly there
and to 7.3-rc7. If that's too late for this cycle, I'm happy to repost
on whatever base you'd like to queue it on.
Thanks,
Liz
prev parent reply other threads:[~2026-10-13 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:40 Liz Fong-Jones
2026-10-02 21:40 ` [PATCH v6 1/3] writeback: clear the old wb's dirty IO state after switching inodes Liz Fong-Jones
2026-10-14 7:35 ` Jan Kara
2026-10-02 21:40 ` [PATCH v6 2/3] writeback: let foreign flushes reach dying cgwbs Liz Fong-Jones
2026-10-14 7:50 ` Jan Kara
2026-10-02 21:40 ` [PATCH v6 3/3] writeback: switch a replaced cgwb's inodes to its successor Liz Fong-Jones
2026-10-14 11:21 ` Jan Kara
2026-10-14 19:05 ` Tejun Heo
2026-10-15 11:45 ` Liz Fong-Jones
2026-10-13 13:34 ` Liz Fong-Jones [this message]
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=20261013133428.725790-1-lizf@honeycomb.io \
--to=lizf@honeycomb.io \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=ian@honeycomb.io \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yinxin.x@bytedance.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
all inboxes | Powered by JetHome®