Re: [PATCH 0/6] Fixes to the previously-merged drivers/dax/fsdev series

[Alison Schofield <alison.schofield@intel.com>]

On Mon, May 18, 2026 at 09:35:15PM +0000, John Groves wrote:
> From: John Groves <john@groves.net>
> 
> This series applies bug fixes (mostly found via sashiko) to the dax/fsdev
> series. This has been soaking in the famfs CI pipeline for 2+ weeks and

I am not able to apply the set to any of 7.1-rc1 through rc4.


> 1) won't affect anything that doesn't use drivers/dax/fsdev.c, and 2)
> doesn't affect any known workloads - although the bugs would have
> manifested when multi-range DCD dax devices are a thing (soon-ish).
> 
> John Groves (6):
>   dax: fix misleading comment about share/index union in
>     dax_folio_reset_order()
>   dax/fsdev: fix multi-range offset, vmemmap_shift leak, and probe error
>     cleanup
>   dax/fsdev: fix kaddr for multi-range and fail probe on invalid pgmap
>     offset
>   dax/fsdev: clamp direct_access return to current physical range
>   dax: fix holder_ops race in fs_put_dax()
>   dax: replace exported dax_dev_get() with non-allocating dax_dev_find()
> 
>  drivers/dax/dax-private.h |  2 -
>  drivers/dax/fsdev.c       | 85 ++++++++++++++++++++++++++++-----------
>  drivers/dax/super.c       | 51 +++++++++++++++++++++--
>  fs/dax.c                  | 12 +++---
>  fs/famfs/famfs_inode.c    |  2 +-
>  fs/fuse/famfs.c           |  2 +-
>  include/linux/dax.h       |  6 ++-
>  7 files changed, 122 insertions(+), 38 deletions(-)
> 
> -- 
> 2.53.0
>