From: Carlos Maiolino <cem@kernel.org>
To: djwong@kernel.org, hch@lst.de, dan.j.williams@intel.com,
willy@infradead.org, jack@suse.cz, brauner@kernel.org,
viro@zeniv.linux.org.uk, John Garry <john.g.garry@oracle.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] xfs and DAX atomic writes changes
Date: Tue, 12 Aug 2025 09:33:22 +0200 [thread overview]
Message-ID: <175498400299.824422.14848821788318521460.b4-ty@kernel.org> (raw)
In-Reply-To: <20250724081215.3943871-1-john.g.garry@oracle.com>
On Thu, 24 Jul 2025 08:12:12 +0000, John Garry wrote:
> This series contains an atomic writes fix for DAX support on xfs and
> an improvement to WARN against using IOCB_ATOMIC on the DAX write path.
>
> Also included is an xfs atomic writes mount option fix.
>
> Based on xfs -next at ("b0494366bd5b Merge branch 'xfs-6.17-merge' into
> for-next")
>
> [...]
Applied to for-next, thanks!
[1/3] fs/dax: Reject IOCB_ATOMIC in dax_iomap_rw()
commit: e7fb9b71326f43bab25fb8f18c6bfebd7a628696
[2/3] xfs: disallow atomic writes on DAX
commit: 68456d05eb57a5d16b4be2d3caf421bdcf2de72e
[3/3] xfs: reject max_atomic_write mount option for no reflink
commit: 8dc5e9b037138317c1d3151a7dabe41fa171cee1
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2025-08-12 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 8:12 John Garry
2025-07-24 8:12 ` [PATCH v3 1/3] fs/dax: Reject IOCB_ATOMIC in dax_iomap_rw() John Garry
2025-07-24 16:25 ` Darrick J. Wong
2025-07-24 8:12 ` [PATCH v3 2/3] xfs: disallow atomic writes on DAX John Garry
2025-07-24 8:12 ` [PATCH v3 3/3] xfs: reject max_atomic_write mount option for no reflink John Garry
2025-07-24 16:32 ` Darrick J. Wong
2025-07-25 8:39 ` John Garry
2025-07-25 15:49 ` Darrick J. Wong
2025-08-06 9:15 ` [PATCH v3 0/3] xfs and DAX atomic writes changes John Garry
2025-08-11 12:06 ` Carlos Maiolino
2025-08-11 12:08 ` John Garry
2025-08-11 12:13 ` Carlos Maiolino
2025-08-12 7:33 ` 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=175498400299.824422.14848821788318521460.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=brauner@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--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
all inboxes | Powered by JetHome®