| Message ID | 167976583114.986322.11327553276111503462.stg-ugh@frogsfrogsfrogs (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [GIT,PULL,1/3] xfs: bug fixes for 6.3-rc2 | expand |
The pull request you sent on Sat, 25 Mar 2023 11:20:47 -0700:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.3-fixes-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1470afefc3c42df5d1662f87d079b46651bdc95b
Thank you!
Hi Linus, Please pull this branch with changes for 6.3-rc2. I've gotten well behind on sending bugfixes, due to ongoing distractions, alas. This batch started with some debugging enhancements to the new allocator refactoring that we put in 6.3-rc1 to assist developers in rebasing their dev branches. As for more serious code changes -- there's a bug fix to make the lockless allocator scan the whole filesystem before resorting to the locking allocator. We're also adding a selftest for the venerable directory/xattr hash function to make sure that it produces consistent results so that we can address any fallout as soon as possible. As usual, I did a test-merge with the main upstream branch as of a few minutes ago, and didn't see any conflicts. Please let me know if you encounter any problems. --D The following changes since commit 8ac5b996bf5199f15b7687ceae989f8b2a410dda: xfs: fix off-by-one-block in xfs_discard_folio() (2023-03-05 15:13:23 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-6.3-fixes-3 for you to fetch changes up to 3cfb9290da3d87a5877b03bda96c3d5d3ed9fcb0: xfs: test dir/attr hash when loading module (2023-03-19 09:55:49 -0700) ---------------------------------------------------------------- Fixes for 6.3-rc2: * Add a few debugging assertions so that people (me) trying to port code to the new allocator functions don't mess up the caller requirements. * Relax some overly cautious lock ordering enforcement in the new allocator code, which means that file allocations will locklessly scan for the best space they can get before backing off to the traditional lock-and-really-get-it behavior. * Add tracepoints to make it easier to trace the xfs allocator behavior. * Actually test the dir/xattr hash algorithm to make sure it produces consistent results across all the platforms XFS supports. Signed-off-by: Darrick J. Wong <djwong@kernel.org> ---------------------------------------------------------------- Darrick J. Wong (4): xfs: try to idiot-proof the allocators xfs: walk all AGs if TRYLOCK passed to xfs_alloc_vextent_iterate_ags xfs: add tracepoints for each of the externally visible allocators xfs: test dir/attr hash when loading module fs/xfs/Makefile | 1 + fs/xfs/libxfs/xfs_alloc.c | 36 ++- fs/xfs/xfs_dahash_test.c | 662 ++++++++++++++++++++++++++++++++++++++++++++++ fs/xfs/xfs_dahash_test.h | 12 + fs/xfs/xfs_super.c | 5 + fs/xfs/xfs_trace.h | 7 + 6 files changed, 722 insertions(+), 1 deletion(-) create mode 100644 fs/xfs/xfs_dahash_test.c create mode 100644 fs/xfs/xfs_dahash_test.h