From: Zach Brown <zab@zabbo.net>
To: Valerie Aurora <val@versity.com>
Cc: rpdfs-devel@lists.linux.dev
Subject: Re: [PATCH] rpdfs: Flush dirty blocks on sync
Date: Wed, 25 Mar 2026 14:39:27 -0700 [thread overview]
Message-ID: <20260325213927.GC990991@localhost.localdomain> (raw)
In-Reply-To: <20260317184203.3980-1-val@versity.com>
On Tue, Mar 17, 2026 at 07:42:03PM +0100, Valerie Aurora wrote:
> Write out dirty blocks when the VFS wants to sync, e.g. when unmounting.
>
> Signed-off-by: Valerie Aurora <val@versity.com>
Applied, thanks!
I'm taking bets on whether we remember to fix up the return 0 once we
wire up io errors through write completion up to the block flush waiters
:).
- z
prev parent reply other threads:[~2026-03-25 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 18:42 [PATCH] rpdfs: Flush dirty blocks on sync Valerie Aurora
2026-03-25 21:39 ` Zach Brown [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=20260325213927.GC990991@localhost.localdomain \
--to=zab@zabbo.net \
--cc=rpdfs-devel@lists.linux.dev \
--cc=val@versity.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.