xfsprogs for-next branch updated
Hello.
The xfsprogs, for-next branch located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/?h=for-next
has just been updated.
The new head is:
b827e2318 xfs: fix sb write verify for lazysbcount
This update contains only the libxfs-sync for Linux 6.1, and will serve as a base for the xfsprogs 6.1 release.
Please, let me know if any issue.
The following commits are now in the for-next tree:
[b827e2318] xfs: fix sb write verify for lazysbcount
[7257eb3ed] xfs: rename XFS_REFC_COW_START to _COWFLAG
[7accbcd00] xfs: fix uninitialized list head in struct xfs_refcount_recovery [8b2b27581] xfs: fix agblocks check in the cow leftover recovery function [817ea9f0f] xfs: check record domain when accessing refcount records [f275d70e8] xfs: remove XFS_FIND_RCEXT_SHARED and _COW
[cc2a3c2ad] xfs: refactor domain and refcount checking
[8160aeff0] xfs: report refcount domain in tracepoints
[6b2f464dd] xfs: track cow/shared record domains explicitly in xfs_refcount_irec [bec88ec72] xfs: move _irec structs to xfs_types.h
[7ccbdec2b] xfs: check deferred refcount op continuation parameters [b3f9ae08e] xfs: create a predicate to verify per-AG extents [2d5166b9d] xfs: make sure aglen never goes negative in xfs_refcount_adjust_extents [4b69afdc4] xfs: refactor all the EFI/EFD log item sizeof logic [d267ac6a0] xfs: fix memcpy fortify errors in EFI log format copying [227bc97f1] xfs: increase rename inode reservation
[20798cc06] xfs: fix exception caused by unexpected illegal bestcount in leaf dir [11d2f5afc] treewide: use get_random_u32() when possible
[4947ac5b3] treewide: use prandom_u32_max() when possible, part 1 [1a3bfffee] xfs: rearrange the logic and remove the broken comment for xfs_dir2_isxx [04d4c27af] xfs: trim the mapp array accordingly in xfs_da_grow_inode_int [e8dbbca18] xfs: Remove the unneeded result variable
[be98db856] xfs: clean up "%Ld/%Lu" which doesn't meet C standard
Signature · 1 line
Carlos Maiolino
Quoted 13 lines · Carlos Maiolino
Hello.
The xfsprogs, for-next branch located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/?h=for-next
has just been updated.
The new head is:
b827e2318xfs: fix sb write verify for lazysbcount
Quoted 8 lines
This update contains only the libxfs-sync for Linux 6.1, and will serve as a base for the xfsprogs 6.1 release.
Please, let me know if any issue.The following commits are now in the for-next tree:
[
b827e2318] xfs: fix sb write verify for lazysbcount
Why was this commit merged for xfsprogs 6.1? That patch is queued for kernel 6.2 in for-next, but the merge window is not open yet.
--D
Quoted 26 lines
[
7257eb3ed] xfs: renameXFS_REFC_COW_STARTto_COWFLAG
[7accbcd00] xfs: fix uninitialized list head in structxfs_refcount_recovery[8b2b27581] xfs: fix agblocks check in the cow leftover recovery function [817ea9f0f] xfs: check record domain when accessing refcount records [f275d70e8] xfs: removeXFS_FIND_RCEXT_SHAREDand_COW
[cc2a3c2ad] xfs: refactor domain and refcount checking
[8160aeff0] xfs: report refcount domain in tracepoints
[6b2f464dd] xfs: track cow/shared record domains explicitly inxfs_refcount_irec[bec88ec72] xfs: move_irecstructs toxfs_types.h
[7ccbdec2b] xfs: check deferred refcount op continuation parameters [b3f9ae08e] xfs: create a predicate to verify per-AG extents [2d5166b9d] xfs: make sure aglen never goes negative inxfs_refcount_adjust_extents[4b69afdc4] xfs: refactor all the EFI/EFD log item sizeof logic [d267ac6a0] xfs: fix memcpy fortify errors in EFI log format copying [227bc97f1] xfs: increase rename inode reservation
[20798cc06] xfs: fix exception caused by unexpected illegal bestcount in leaf dir [11d2f5afc] treewide: useget_random_u32()when possible
[4947ac5b3] treewide: useprandom_u32_max()when possible, part 1 [1a3bfffee] xfs: rearrange the logic and remove the broken comment forxfs_dir2_isxx[04d4c27af] xfs: trim the mapp array accordingly inxfs_da_grow_inode_int[e8dbbca18] xfs: Remove the unneeded result variable
[be98db856] xfs: clean up "%Ld/%Lu" which doesn't meet C standardSignature · 1 line
Carlos Maiolino
Quoted 19 lines · Darrick J. Wong
Quoted 18 lines · Carlos Maiolino
Hello.
The xfsprogs, for-next branch located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/?h=for-next
has just been updated.
The new head is:
b827e2318xfs: fix sb write verify for lazysbcountThis update contains only the libxfs-sync for Linux 6.1, and will serve as a base for the xfsprogs 6.1 release.
Please, let me know if any issue.
Quoted 7 lines
Quoted 3 lines
The following commits are now in the for-next tree:
[
b827e2318] xfs: fix sb write verify for lazysbcountWhy was this commit merged for xfsprogs 6.1? That patch is queued for kernel 6.2 in for-next, but the merge window is not open yet.
Since 6.1 isn't out yet, I did a libxfs-apply <last libxfscommit>.., my fault for not spotting you've patches already queued for 6.2. I'm planning to release xfsprogs-6.1 some time later after linux 6.1 is out, so this patch will already be in Linus's tree by the time. I can also get this patch out of the tree when I push the other patches I have queued up, although I'm trying to avoid doing forced updates to the tree. Is it ok for you to leave it in the tree, or better remove it by now?
Cheers
Signature · 1 line
Carlos Maiolino
Quoted 28 lines · Carlos Maiolino
Quoted 19 lines · Darrick J. Wong
Quoted 18 lines · Carlos Maiolino
Hello.
The xfsprogs, for-next branch located at:
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/log/?h=for-next
has just been updated.
The new head is:
b827e2318xfs: fix sb write verify for lazysbcountThis update contains only the libxfs-sync for Linux 6.1, and will serve as a base for the xfsprogs 6.1 release.
Please, let me know if any issue.Quoted 7 lines
Quoted 3 lines
The following commits are now in the for-next tree:
[
b827e2318] xfs: fix sb write verify for lazysbcountWhy was this commit merged for xfsprogs 6.1? That patch is queued for kernel 6.2 in for-next, but the merge window is not open yet.
Quoted 7 lines
Since 6.1 isn't out yet, I did a
libxfs-apply <last libxfscommit>.., my fault for not spotting you've patches already queued for 6.2. I'm planning to release xfsprogs-6.1 some time later after linux 6.1 is out, so this patch will already be in Linus's tree by the time. I can also get this patch out of the tree when I push the other patches I have queued up, although I'm trying to avoid doing forced updates to the tree. Is it ok for you to leave it in the tree, or better remove it by now?
For this one patch it doesn't matter since the race only happens when there are multiple threads updating the inode summary counts. Userspace doesn't do any concurrent inobt updates, so the fix arriving early ought to be benign.
(That said, the only thing you have to do if you push -f is let everyone know that for-next has been **REBASED**, but I agree with the sentiment of only doing it when it's really important.)
--D
Quoted 4 lines
Cheers
Signature · 1 line
Carlos Maiolino