From: Carlos Maiolino <cem@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Chris Mason <mason@kernel.org>,
tytso@mit.edu, david@fromorbit.com, jack@suse.cz,
djwong@kernel.org, josef@toxicpanda.com, hch@lst.de,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v6 04/10] iomap: don't punch delalloc under a dirty EOF block
Date: Wed, 11 Nov 2026 14:24:09 +0100 [thread overview]
Message-ID: <avRsclSj-Es5AxCf@cronus.toxiclabs.cc> (raw)
In-Reply-To: <20261111-esskultur-nahebringen-beiwerk-4a8a3b77bbf1@brauner>
On Wed, Nov 11, 2026 at 12:21:35PM +0100, Christian Brauner wrote:
> On Tue, Nov 10, 2026 at 10:43:37AM +0100, Carlos Maiolino wrote:
> > Christian, is it ok with you if I pull this through xfs tree?
>
> Sure,
> Acked-by: Christian Brauner <brauner@kernel.org>
Thanks!
>
> --
>
next prev parent reply other threads:[~2026-11-11 13:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 23:51 [PATCH v6 00/10] reflink and atomic write bugs Chris Mason
2026-11-09 23:51 ` [PATCH v6 01/10] xfs: don't skip the flush before shifting extents Chris Mason
2026-11-09 23:51 ` [PATCH v6 02/10] xfs: flush the shifted range before changing the file Chris Mason
2026-11-09 23:51 ` [PATCH v6 03/10] xfs: don't change the block map under a dirty folio Chris Mason
2026-11-09 23:51 ` [PATCH v6 04/10] iomap: don't punch delalloc under a dirty EOF block Chris Mason
2026-11-10 9:43 ` Carlos Maiolino
2026-11-11 11:21 ` Christian Brauner
2026-11-11 13:24 ` Carlos Maiolino [this message]
2026-11-09 23:51 ` [PATCH v6 05/10] fs: validate atomic writes after O_APPEND and limits Chris Mason
2026-11-10 9:41 ` Carlos Maiolino
2026-11-10 15:26 ` Chris Mason
2026-11-10 16:20 ` Carlos Maiolino
2026-11-09 23:51 ` [PATCH v6 06/10] xfs: recheck direct write alignment after write checks Chris Mason
2026-11-09 23:51 ` [PATCH v6 07/10] xfs: test for reflink after the dio " Chris Mason
2026-11-09 23:51 ` [PATCH v6 08/10] xfs: refuse writes to files racing with realtime inode flag changes Chris Mason
2026-11-09 23:51 ` [PATCH v6 09/10] xfs: refuse fallocate racing with realtime " Chris Mason
2026-11-09 23:51 ` [PATCH v6 10/10] xfs: restart faults " Chris Mason
2026-11-10 9:45 ` [PATCH v6 00/10] reflink and atomic write bugs Carlos Maiolino
2026-11-10 15:56 ` Chris Mason
2026-11-10 16:22 ` Carlos Maiolino
2026-11-10 16:32 ` Chris Mason
2026-11-10 17:00 ` Carlos Maiolino
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=avRsclSj-Es5AxCf@cronus.toxiclabs.cc \
--to=cem@kernel.org \
--cc=brauner@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mason@kernel.org \
--cc=tytso@mit.edu \
/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.