From: Carlos Maiolino <cem@kernel.org>
To: hch@infradead.org, dchinner@redhat.com,
Hongling Zeng <zenghongling@kylinos.cn>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
zhongling0719@126.com
Subject: Re: [PATCH v3] xfs: use file target for post-log fsync fallback flush
Date: Mon, 10 Aug 2026 13:55:36 +0200 [thread overview]
Message-ID: <178636293674.58486.4052821152223615651.b4-ty@kernel.org> (raw)
In-Reply-To: <20260730084236.173288-1-zenghongling@kylinos.cn>
On Thu, 30 Jul 2026 16:42:36 +0800, Hongling Zeng wrote:
> xfs_file_fsync() has a fallback flush for the case where the log force
> was a no-op, for example fdatasync/O_DSYNC writes that do not require
> metadata updates. The current fallback path is expressed in terms of the
> main data device and explicitly excludes realtime inodes.
>
> Realtime files with a separate realtime device are flushed before the log
> force, because their data must reach stable storage before the log commit.
> For the internal realtime device used by the zoned allocator, writes are
> out-of-place and update inode and bmap metadata from I/O completion, so
> the overwrite-without-metadata-update case does not apply in the same way.
>
> [...]
Applied to for-next, thanks!
[1/1] xfs: use file target for post-log fsync fallback flush
commit: a94e648f03cf4e0def8ab3c74a1f9fe140720dd4
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-08-10 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 8:42 Hongling Zeng
2026-07-30 8:48 ` Christoph Hellwig
2026-08-10 11:55 ` Carlos Maiolino [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=178636293674.58486.4052821152223615651.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zenghongling@kylinos.cn \
--cc=zhongling0719@126.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®