public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: ruansy.fnst@fujitsu.com, linux-fsdevel@vger.kernel.org,
	hch@lst.de, linux-xfs@vger.kernel.org, willy@infradead.org,
	cem@kernel.org
Subject: Re: [PATCHSET] fsdax/xfs: unshare range fixes for 6.12
Date: Fri, 25 Oct 2024 15:24:44 -0700	[thread overview]
Message-ID: <20241025222444.GM21836@frogsfrogsfrogs> (raw)
In-Reply-To: <20241007-ortstarif-zeugnis-bfffcb7177aa@brauner>

On Mon, Oct 07, 2024 at 01:52:18PM +0200, Christian Brauner wrote:
> On Thu, 03 Oct 2024 08:08:55 -0700, Darrick J. Wong wrote:
> > This patchset fixes multiple data corruption bugs in the fallocate unshare
> > range implementation for fsdax.
> > 
> > With a bit of luck, this should all go splendidly.
> > Comments and questions are, as always, welcome.
> > 
> > --D
> > 
> > [...]
> 
> Applied to the vfs.iomap branch of the vfs/vfs.git tree.
> Patches in the vfs.iomap branch should appear in linux-next soon.

Er, this has been soaking for 18 days, is it going in soon?
(Apologies, I just saw that you've been under the weather.)

--D

> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
> 
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
> 
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs.iomap
> 
> [1/4] xfs: don't allocate COW extents when unsharing a hole
>       https://git.kernel.org/vfs/vfs/c/b8c4076db5fd
> [2/4] iomap: share iomap_unshare_iter predicate code with fsdax
>       https://git.kernel.org/vfs/vfs/c/6ef6a0e821d3
> [3/4] fsdax: remove zeroing code from dax_unshare_iter
>       https://git.kernel.org/vfs/vfs/c/95472274b6fe
> [4/4] fsdax: dax_unshare_iter needs to copy entire blocks
>       https://git.kernel.org/vfs/vfs/c/50793801fc7f
> 

  reply	other threads:[~2024-10-25 22:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03 15:08 [PATCHSET] fsdax/xfs: unshare range fixes for 6.12 Darrick J. Wong
2024-10-03 15:09 ` [PATCH 1/4] xfs: don't allocate COW extents when unsharing a hole Darrick J. Wong
2024-10-04 12:07   ` Christoph Hellwig
2024-10-03 15:09 ` [PATCH 2/4] iomap: share iomap_unshare_iter predicate code with fsdax Darrick J. Wong
2024-10-04 12:07   ` Christoph Hellwig
2024-10-03 15:09 ` [PATCH 3/4] fsdax: remove zeroing code from dax_unshare_iter Darrick J. Wong
2024-10-04 12:09   ` Christoph Hellwig
2024-10-03 15:09 ` [PATCH 4/4] fsdax: dax_unshare_iter needs to copy entire blocks Darrick J. Wong
2024-10-04 12:09   ` Christoph Hellwig
2024-10-07 11:52 ` [PATCHSET] fsdax/xfs: unshare range fixes for 6.12 Christian Brauner
2024-10-25 22:24   ` Darrick J. Wong [this message]
2024-10-28 11:14     ` Christian Brauner
  -- strict thread matches above, loose matches on Subject: below --
2024-10-03 15:08 Darrick J. Wong

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=20241025222444.GM21836@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cem@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ruansy.fnst@fujitsu.com \
    --cc=willy@infradead.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