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")

John Garry (3):
  fs/dax: Reject IOCB_ATOMIC in dax_iomap_rw()
  xfs: disallow atomic writes on DAX
  xfs: reject max_atomic_write mount option for no reflink

 fs/dax.c           |  3 +++
 fs/xfs/xfs_file.c  |  6 +++---
 fs/xfs/xfs_inode.h | 11 +++++++++++
 fs/xfs/xfs_iops.c  |  5 +++--
 fs/xfs/xfs_mount.c | 19 +++++++++++++++++++
 5 files changed, 39 insertions(+), 5 deletions(-)

-- 
2.43.5

On 24/07/2025 09:12, John Garry wrote:

Hi Carlos,

I was expecting you to pick these up.

Shall I resend next week after v6.17-rc1 is released?

Thanks,
John

> 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")
> 
> John Garry (3):
>    fs/dax: Reject IOCB_ATOMIC in dax_iomap_rw()
>    xfs: disallow atomic writes on DAX
>    xfs: reject max_atomic_write mount option for no reflink
> 
>   fs/dax.c           |  3 +++
>   fs/xfs/xfs_file.c  |  6 +++---
>   fs/xfs/xfs_inode.h | 11 +++++++++++
>   fs/xfs/xfs_iops.c  |  5 +++--
>   fs/xfs/xfs_mount.c | 19 +++++++++++++++++++
>   5 files changed, 39 insertions(+), 5 deletions(-)
>

On Wed, Aug 06, 2025 at 10:15:10AM +0100, John Garry wrote:
> On 24/07/2025 09:12, John Garry wrote:
> 
> Hi Carlos,
> 
> I was expecting you to pick these up.

I did, for -rc1.

> 
> Shall I resend next week after v6.17-rc1 is released?

No, I already have them queued up for -rc1, no need to send them again

Carlos

> 
> Thanks,
> John
> 
> > 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")
> >
> > John Garry (3):
> >    fs/dax: Reject IOCB_ATOMIC in dax_iomap_rw()
> >    xfs: disallow atomic writes on DAX
> >    xfs: reject max_atomic_write mount option for no reflink
> >
> >   fs/dax.c           |  3 +++
> >   fs/xfs/xfs_file.c  |  6 +++---
> >   fs/xfs/xfs_inode.h | 11 +++++++++++
> >   fs/xfs/xfs_iops.c  |  5 +++--
> >   fs/xfs/xfs_mount.c | 19 +++++++++++++++++++
> >   5 files changed, 39 insertions(+), 5 deletions(-)
> >
> 
>

On 11/08/2025 13:06, Carlos Maiolino wrote:
>> I was expecting you to pick these up.
> I did, for -rc1.
> 
>> Shall I resend next week after v6.17-rc1 is released?
> No, I already have them queued up for -rc1, no need to send them again

Great, thanks. I was just prepping to send again :)

On Mon, Aug 11, 2025 at 01:08:59PM +0100, John Garry wrote:
> On 11/08/2025 13:06, Carlos Maiolino wrote:
> >> I was expecting you to pick these up.
> > I did, for -rc1.
> >
> >> Shall I resend next week after v6.17-rc1 is released?
> > No, I already have them queued up for -rc1, no need to send them again
> 
> Great, thanks. I was just prepping to send again :)

Sorry, I meant I have them queued up for -rc2 :-) i.e. this week I'm
sending them to Linus

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>