public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
	 Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH v4 0/8] iomap, xfs: improve zero range flushing and lookup
Date: Mon, 23 Mar 2026 11:47:19 +0100	[thread overview]
Message-ID: <177426283968.254917.17482470861788791651.b4-ty@kernel.org> (raw)
In-Reply-To: <20260311162502.192375-1-bfoster@redhat.com>

On Wed, 11 Mar 2026 12:24:54 -0400, Brian Foster wrote:
> No significant changes in v4. A few whitespace fixes throughout and I've
> added some R-b tags from v3 review. Thanks.
> 
> Brian
> 
> v4:
> - Minor whitespace cleanups.
> v3: https://lore.kernel.org/linux-fsdevel/20260309134506.167663-1-bfoster@redhat.com/
> - Inserted new patches 1-2 to fix up zoned mode zeroing.
> - Appended patch 8 to correctly report COW mappings backed by data fork
>   holes.
> - Various minor fixups to logic, whitespace, comments.
> v2: https://lore.kernel.org/linux-fsdevel/20260129155028.141110-1-bfoster@redhat.com/
> - Patch 1 from v1 merged separately.
> - Fixed up iomap_fill_dirty_folios() call in patch 5.
> v1: https://lore.kernel.org/linux-fsdevel/20251016190303.53881-1-bfoster@redhat.com/
> 
> [...]

Applied to for-next, thanks!

[1/8] xfs: fix iomap hole map reporting for zoned zero range
      commit: 92e9dff9ca5026805798b13b967760f8058794e8
[2/8] xfs: flush dirty pagecache over hole in zoned mode zero range
      commit: 2f46c239fce617ac26cc40d9520b1c0cf05cd34f
[3/8] iomap, xfs: lift zero range hole mapping flush into xfs
      commit: a35bb0dec9552aa2bc69a24e3126c68c257bf55e
[4/8] xfs: flush eof folio before insert range size update
      commit: c35a3e273e86e89f73abc4e75e33648fac20eec9
[5/8] xfs: look up cow fork extent earlier for buffered iomap_begin
      commit: a8eb41376df987887b33dbf7078d5b13c85f3e0c
[6/8] xfs: only flush when COW fork blocks overlap data fork holes
      commit: c770f997a4227b6fc5f62275b2337622213e35af
[7/8] xfs: replace zero range flush with folio batch
      commit: ce9d27ca8b2eafdd2457a15aafdab74218843138
[8/8] xfs: report cow mappings with dirty pagecache for iomap zero range
      commit: 388bb26b3d33de3c53a492824a4c5804151a0014

Best regards,
-- 
Carlos Maiolino <cem@kernel.org>


      parent reply	other threads:[~2026-03-23 10:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 16:24 [PATCH v4 0/8] iomap, xfs: improve zero range flushing and lookup Brian Foster
2026-03-11 16:24 ` [PATCH v4 1/8] xfs: fix iomap hole map reporting for zoned zero range Brian Foster
2026-03-11 16:24 ` [PATCH v4 2/8] xfs: flush dirty pagecache over hole in zoned mode " Brian Foster
2026-03-11 22:14   ` Darrick J. Wong
2026-03-11 16:24 ` [PATCH v4 3/8] iomap, xfs: lift zero range hole mapping flush into xfs Brian Foster
2026-03-11 16:24 ` [PATCH v4 4/8] xfs: flush eof folio before insert range size update Brian Foster
2026-03-11 21:36   ` Darrick J. Wong
2026-03-11 16:24 ` [PATCH v4 5/8] xfs: look up cow fork extent earlier for buffered iomap_begin Brian Foster
2026-03-11 16:25 ` [PATCH v4 6/8] xfs: only flush when COW fork blocks overlap data fork holes Brian Foster
2026-03-11 16:25 ` [PATCH v4 7/8] xfs: replace zero range flush with folio batch Brian Foster
2026-03-11 16:25 ` [PATCH v4 8/8] xfs: report cow mappings with dirty pagecache for iomap zero range Brian Foster
2026-03-12  6:55   ` Christoph Hellwig
2026-03-18  9:13 ` [PATCH v4 0/8] iomap, xfs: improve zero range flushing and lookup Carlos Maiolino
2026-03-18  9:40   ` Christian Brauner
2026-03-23 10:47 ` 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=177426283968.254917.17482470861788791651.b4-ty@kernel.org \
    --to=cem@kernel.org \
    --cc=bfoster@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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