xfs-linux: for-next updated to a24cae8fc1f1
Hi folks,
The for-next branch of the xfs-linux repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches were in this update. If they have not been in this update, please resubmit them to [email protected] so they can be picked up in the next update.
The new head of the for-next branch is commit:
a24cae8fc1f1 xfs: reset rootdir extent size hint after growfsrt
9 new commits:
Darrick J. Wong (6):
[e21fea4ac3cf] xfs: fix di_onlink checking for V1/V2 inodes [5335affcff91] xfs: fix folio dirtying for XFILE_ALLOC callers [410e8a18f8e9] xfs: don't bother reporting blocks trimmed via FITRIM [6b35cc8d9239] xfs: use XFS_BUF_DADDR_NULL for daddrs in getfsmap code [16e1fbdce9c8] xfs: take m_growlock when running growfsrt [a24cae8fc1f1] xfs: reset rootdir extent size hint after growfsrt
Dave Chinner (1):
[95179935bead] xfs: xfs_finobt_count_blocks() walks the wrong btree
Zizhi Wo (2):
[68415b349f3f] xfs: Fix the owner setting issue for rmap query in xfs fsmap [ca6448aed4f1] xfs: Fix missing interval for missing_owner in xfs fsmap
Code Diffstat:
fs/xfs/libxfs/xfs_ialloc_btree.c | 2 +- fs/xfs/libxfs/xfs_inode_buf.c | 14 +++-- fs/xfs/scrub/xfile.c | 2 +- fs/xfs/xfs_discard.c | 36 ++++-------- fs/xfs/xfs_fsmap.c | 30 ++++++++-- fs/xfs/xfs_rtalloc.c | 78 ++++++++++++++++++++----- 6 files changed, 114 insertions(+), 48 deletions(-)
Since 6.10 is still marked as a stable release, maybe this shold go into 6.10-fixes branch as well?
Dave Chinner (1):
[95179935bead] xfs: xfs_finobt_count_blocks() walks the wrong btree
/Anders
Quoted 43 lines · Chandan Babu R
Hi folks,
The for-next branch of the xfs-linux repository at:
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding patches were in this update. If they have not been in this update, please resubmit them to [email protected] so they can be picked up in the next update.
The new head of the for-next branch is commit:
a24cae8fc1f1xfs: reset rootdir extent size hint after growfsrt9 new commits:
Darrick J. Wong (6):
[e21fea4ac3cf] xfs: fixdi_onlinkchecking for V1/V2 inodes [5335affcff91] xfs: fix folio dirtying forXFILE_ALLOCcallers [410e8a18f8e9] xfs: don't bother reporting blocks trimmed via FITRIM [6b35cc8d9239] xfs: useXFS_BUF_DADDR_NULLfor daddrs in getfsmap code [16e1fbdce9c8] xfs: takem_growlockwhen running growfsrt [a24cae8fc1f1] xfs: reset rootdir extent size hint after growfsrtDave Chinner (1):
[95179935bead] xfs:xfs_finobt_count_blocks()walks the wrong btreeZizhi Wo (2):
[68415b349f3f] xfs: Fix the owner setting issue for rmap query in xfs fsmap [ca6448aed4f1] xfs: Fix missing interval formissing_ownerin xfs fsmapCode Diffstat:
fs/xfs/libxfs/xfs_ialloc_btree.c | 2 +- fs/xfs/libxfs/xfs_inode_buf.c | 14 +++-- fs/xfs/scrub/xfile.c | 2 +- fs/xfs/xfs_discard.c | 36 ++++-------- fs/xfs/xfs_fsmap.c | 30 ++++++++-- fs/xfs/xfs_rtalloc.c | 78 ++++++++++++++++++++----- 6 files changed, 114 insertions(+), 48 deletions(-)
Quoted 5 lines · Anders Blomdell
Since 6.10 is still marked as a stable release, maybe this shold go into 6.10-fixes branch as well?
Dave Chinner (1):
[95179935bead] xfs:xfs_finobt_count_blocks()walks the wrong btree
xfs-linux git repository's xfs-6.10-fixes is not meant for collecting patches for stable kernels.
Also, the patch mentioned above cannot be merged into 6.10.y for the following reasons:
1. The 6.11 kernel has not been released yet.
2. No developer has signed up for backporting patches to 6.10.y.
Signature · 1 line
Chandan
Dave,
Do you mind if I CC the path to [email protected] (and maybe GKH)?
/Anders
Quoted 15 lines · Chandan Babu R
Quoted 5 lines · Anders Blomdell
Since 6.10 is still marked as a stable release, maybe this shold go into 6.10-fixes branch as well?
Dave Chinner (1):
[95179935bead] xfs:xfs_finobt_count_blocks()walks the wrong btreexfs-linux git repository's xfs-6.10-fixes is not meant for collecting patches for stable kernels.
Also, the patch mentioned above cannot be merged into 6.10.y for the following reasons:
1. The 6.11 kernel has not been released yet.
2. No developer has signed up for backporting patches to 6.10.y.
Quoted 3 lines · Anders Blomdell
Dave,
Do you mind if I CC the path to [email protected] (and maybe GKH)?
Go ahead - I missed putting the stable cc in the patch itself which would have triggered an automatic stable kernel backport when it got merged into the mainline tree.
-Dave.
Signature · 2 lines
Dave Chinner [email protected]