[6.6,00/24] xfs backports for 6.6.y (from 6.8)

Message

Catherine Hoang March 27, 2024, 12:12 a.m. UTC

Hello,

This series contains backports for 6.6 from the 6.8 release. This patchset
has gone through xfs testing and review.

Andrey Albershteyn (1):
  xfs: reset XFS_ATTR_INCOMPLETE filter on node removal

Christoph Hellwig (1):
  xfs: consider minlen sized extents in xfs_rtallocate_extent_block

Darrick J. Wong (16):
  xfs: move the xfs_rtbitmap.c declarations to xfs_rtbitmap.h
  xfs: convert rt bitmap extent lengths to xfs_rtbxlen_t
  xfs: don't leak recovered attri intent items
  xfs: use xfs_defer_pending objects to recover intent items
  xfs: pass the xfs_defer_pending object to iop_recover
  xfs: transfer recovered intent item ownership in ->iop_recover
  xfs: make rextslog computation consistent with mkfs
  xfs: fix 32-bit truncation in xfs_compute_rextslog
  xfs: don't allow overly small or large realtime volumes
  xfs: make xchk_iget safer in the presence of corrupt inode btrees
  xfs: remove unused fields from struct xbtree_ifakeroot
  xfs: recompute growfsrtfree transaction reservation while growing rt
    volume
  xfs: fix an off-by-one error in xreap_agextent_binval
  xfs: force all buffers to be written during btree bulk load
  xfs: add missing nrext64 inode flag check to scrub
  xfs: remove conditional building of rt geometry validator functions

Dave Chinner (1):
  xfs: initialise di_crc in xfs_log_dinode

Eric Sandeen (1):
  xfs: short circuit xfs_growfs_data_private() if delta is zero

Jiachen Zhang (1):
  xfs: ensure logflagsp is initialized in xfs_bmap_del_extent_real

Long Li (2):
  xfs: add lock protection when remove perag from radix tree
  xfs: fix perag leak when growfs fails

Zhang Tianci (1):
  xfs: update dir3 leaf block metadata after swap

 fs/xfs/libxfs/xfs_ag.c            |  36 +++++++--
 fs/xfs/libxfs/xfs_ag.h            |   2 +
 fs/xfs/libxfs/xfs_attr.c          |   6 +-
 fs/xfs/libxfs/xfs_bmap.c          |  75 ++++++++-----------
 fs/xfs/libxfs/xfs_btree_staging.c |   4 +-
 fs/xfs/libxfs/xfs_btree_staging.h |   6 --
 fs/xfs/libxfs/xfs_da_btree.c      |   7 ++
 fs/xfs/libxfs/xfs_defer.c         | 105 +++++++++++++++++++-------
 fs/xfs/libxfs/xfs_defer.h         |   5 ++
 fs/xfs/libxfs/xfs_format.h        |   2 +-
 fs/xfs/libxfs/xfs_log_recover.h   |   5 ++
 fs/xfs/libxfs/xfs_rtbitmap.c      |   2 +
 fs/xfs/libxfs/xfs_rtbitmap.h      |  83 +++++++++++++++++++++
 fs/xfs/libxfs/xfs_sb.c            |  20 ++++-
 fs/xfs/libxfs/xfs_sb.h            |   2 +
 fs/xfs/libxfs/xfs_types.h         |  13 ++++
 fs/xfs/scrub/common.c             |   6 +-
 fs/xfs/scrub/common.h             |  25 +++++++
 fs/xfs/scrub/fscounters.c         |   2 +-
 fs/xfs/scrub/inode.c              |   8 +-
 fs/xfs/scrub/reap.c               |   2 +-
 fs/xfs/scrub/rtbitmap.c           |   3 +-
 fs/xfs/scrub/rtsummary.c          |   3 +-
 fs/xfs/scrub/trace.h              |   3 +-
 fs/xfs/xfs_attr_item.c            |  23 +++---
 fs/xfs/xfs_bmap_item.c            |  14 ++--
 fs/xfs/xfs_buf.c                  |  44 ++++++++++-
 fs/xfs/xfs_buf.h                  |   1 +
 fs/xfs/xfs_extfree_item.c         |  14 ++--
 fs/xfs/xfs_fsmap.c                |   2 +-
 fs/xfs/xfs_fsops.c                |   9 ++-
 fs/xfs/xfs_inode_item.c           |   3 +
 fs/xfs/xfs_log.c                  |   1 +
 fs/xfs/xfs_log_priv.h             |   1 +
 fs/xfs/xfs_log_recover.c          | 118 ++++++++++++++++--------------
 fs/xfs/xfs_refcount_item.c        |  13 ++--
 fs/xfs/xfs_rmap_item.c            |  14 ++--
 fs/xfs/xfs_rtalloc.c              |  14 +++-
 fs/xfs/xfs_rtalloc.h              |  73 ------------------
 fs/xfs/xfs_trans.h                |   4 +-
 40 files changed, 492 insertions(+), 281 deletions(-)
 create mode 100644 fs/xfs/libxfs/xfs_rtbitmap.h

Comments

Greg KH March 29, 2024, 9:52 a.m. UTC | #1

On Tue, Mar 26, 2024 at 05:12:09PM -0700, Catherine Hoang wrote:
> Hello,
> 
> This series contains backports for 6.6 from the 6.8 release. This patchset
> has gone through xfs testing and review.

Normally we want fixes for newer stable kernels too, i.e. 6.7.y, as you
never want someone to upgrade and have a regression.

But as the next 6.7 release will be the last one, it's probably fine
here, so I'll just take these for now.  But be aware of this in the
future please.

thanks,

greg k-h