From: "Darrick J. Wong" <djwong@kernel.org>
To: cem@kernel.org
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 11/14] xfarray: don't allow users to unset in the middle of an array
Date: Tue, 22 Sep 2026 11:14:33 -0700 [thread overview]
Message-ID: <20260922181433.GA2705364@frogsfrogsfrogs> (raw)
In-Reply-To: <178996120785.181988.9998461891697022684.stgit@frogsfrogsfrogs>
On Sun, Sep 20, 2026 at 11:17:51PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Now that we've merged online fsck, the only user of xfarray_unset is the
> free space btree repair code, and it only needs to be able to remove
> records from the end of the array. Let's remove all the code that
> handles "unset" array elements that are not at the end, because we can
> just reduce the array element count.
>
> Remove the "store anywhere" function because it was only ever used by
> the callers who used unset to remove elements in the middle of the
> array.
>
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
> fs/xfs/scrub/xfarray.h | 6 -
> .../filesystems/xfs/xfs-online-fsck-design.rst | 13 +--
> fs/xfs/scrub/alloc_repair.c | 2
> fs/xfs/scrub/xfarray.c | 92 ++------------------
> 4 files changed, 14 insertions(+), 99 deletions(-)
>
>
> diff --git a/fs/xfs/scrub/xfarray.h b/fs/xfs/scrub/xfarray.h
> index 5eeeeed13ae24a..d55225c7885b25 100644
> --- a/fs/xfs/scrub/xfarray.h
> +++ b/fs/xfs/scrub/xfarray.h
> @@ -27,9 +27,6 @@ struct xfarray {
> /* Maximum possible array size. */
> xfarray_idx_t max_nr;
>
> - /* Number of unset slots in the array below @nr. */
> - uint64_t unset_slots;
> -
> /* Size of an array element. */
> size_t obj_size;
>
> @@ -41,9 +38,8 @@ int xfarray_create(const char *descr, unsigned long long required_capacity,
> size_t obj_size, struct xfarray **arrayp);
> void xfarray_destroy(struct xfarray *array);
> int xfarray_load(struct xfarray *array, xfarray_idx_t idx, void *ptr);
> -int xfarray_unset(struct xfarray *array, xfarray_idx_t idx);
> +int xfarray_trim(struct xfarray *array, unsigned long long nr);
> int xfarray_store(struct xfarray *array, xfarray_idx_t idx, const void *ptr);
> -int xfarray_store_anywhere(struct xfarray *array, const void *ptr);
> bool xfarray_element_is_null(struct xfarray *array, const void *ptr);
> void xfarray_truncate(struct xfarray *array);
> unsigned long long xfarray_bytes(struct xfarray *array);
> diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> index 3d9233f403dbb1..14767ce9fad43f 100644
> --- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> +++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> @@ -1973,8 +1973,7 @@ provide loading and storing of array elements at arbitrary array indices.
> Gaps are defined to be null records, and null records are defined to be a
> sequence of all zero bytes.
> Null records are detected by calling ``xfarray_element_is_null``.
> -They are created either by calling ``xfarray_unset`` to null out an existing
> -record or by never storing anything to an array index.
> +They are created by never storing anything to an array index.
>
> The second type of caller handles records that are not indexed by position
> and do not require multiple updates to a record.
> @@ -1991,9 +1990,7 @@ The typical use case here is constructing space extent reference counts from
> reverse mapping information.
> Records can be put in the bag in any order, they can be removed from the bag
> at any time, and uniqueness of records is left to callers.
> -The ``xfarray_store_anywhere`` function is used to insert a record in any
> -null record slot in the bag; and the ``xfarray_unset`` function removes a
> -record from the bag.
> +Note: Bags are now implemented with in-memory btrees for faster access.
>
> Iterating Array Elements
> ^^^^^^^^^^^^^^^^^^^^^^^^
> @@ -2643,11 +2640,7 @@ generate refcount information from reverse mapping records.
> refcount record associating the block number range that we just walked to
> the size of the bag.
>
> -The bag-like structure in this case is a type 2 xfarray as discussed in the
> -:ref:`xfarray access patterns<xfarray_access_patterns>` section.
> -Reverse mappings are added to the bag using ``xfarray_store_anywhere`` and
> -removed via ``xfarray_unset``.
> -Bag members are examined through ``xfarray_iter`` loops.
> +The bag-like structure in this case is an in-memory btree.
>
> Case Study: Rebuilding File Fork Mapping Indices
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> diff --git a/fs/xfs/scrub/alloc_repair.c b/fs/xfs/scrub/alloc_repair.c
> index 95e318e4f3a6c7..b37b80af52a03b 100644
> --- a/fs/xfs/scrub/alloc_repair.c
> +++ b/fs/xfs/scrub/alloc_repair.c
> @@ -517,7 +517,7 @@ xrep_abt_reserve_space(
> * records (but doesn't break the sorting order), so we must
> * go around the loop once more to re-run _bload_init.
> */
> - error = xfarray_unset(ra->free_records, record_nr);
> + error = xfarray_trim(ra->free_records, 1);
> if (error)
> break;
> ra->nr_real_records--;
> diff --git a/fs/xfs/scrub/xfarray.c b/fs/xfs/scrub/xfarray.c
> index 30a58e9d4378e4..ee3f0bf87433f1 100644
> --- a/fs/xfs/scrub/xfarray.c
> +++ b/fs/xfs/scrub/xfarray.c
> @@ -149,9 +149,6 @@ xfarray_is_unset(
Shashiko writes:
"Is this function now entirely dead code? The patch removes xfarray_unset(),
which was the only caller of the xfarray_is_unset() static inline helper.
Should the entire xfarray_is_unset() function be removed?"
Yes.
> void *temp = xfarray_scratch(array);
> int error;
>
> - if (array->unset_slots == 0)
> - return false;
> -
> error = xfile_load(array->xfile, temp, array->obj_size, pos);
> if (!error && xfarray_element_is_null(array, temp))
> return true;
> @@ -159,36 +156,18 @@ xfarray_is_unset(
> return false;
> }
>
> -/*
> - * Unset an array element. If @idx is the last element in the array, the
> - * array will be truncated. Otherwise, the entry will be zeroed.
> - */
> +/* Remove the elements at the end of an array. */
> int
> -xfarray_unset(
> - struct xfarray *array,
> - xfarray_idx_t idx)
> +xfarray_trim(
> + struct xfarray *array,
> + unsigned long long nr)
> {
> - void *temp = xfarray_scratch(array);
> - loff_t pos = xfarray_pos(array, idx);
> - int error;
> -
> - if (idx >= array->nr)
> + if (nr > array->nr)
> return -ENODATA;
>
> - if (idx == array->nr - 1) {
> - array->nr--;
> - return 0;
> - }
> -
> - if (xfarray_is_unset(array, pos))
> - return 0;
> -
> - memset(temp, 0, array->obj_size);
> - error = xfile_store(array->xfile, temp, array->obj_size, pos);
> - if (error)
> - return error;
> -
> - array->unset_slots++;
> + array->nr -= nr;
> + xfile_discard(array->xfile, xfarray_pos(array, array->nr),
> + MAX_LFS_FILESIZE);
"Can passing MAX_LFS_FILESIZE here cause a silent memory leak on 32-bit
architectures?
In xfarray_trim(), MAX_LFS_FILESIZE is passed as the count to
xfile_discard(), which passes it directly to shmem_truncate_range().
On 32-bit systems, MAX_LFS_FILESIZE is 0xFFFFFFFF000. When pos >= 0x1000
(4KB), the lend calculation (pos + count - 1) inside shmem_undo_range()
evaluates to at least 0x100000000000.
The truncation endpoint is calculated as:
end = (lend + 1) >> PAGE_SHIFT;
This results in an end value of 0x100000000. Since pgoff_t is a 32-bit
unsigned long on 32-bit systems, this truncates to exactly 0.
Because start would be at least 1, the loop "while (index < end)" evaluates
1 < 0, which is false. The loop terminates immediately without discarding any
pages, causing a memory leak during XFS free space btree repair.
Should count be clamped, such as passing MAX_LFS_FILESIZE - pos?"
Yes.
--D
> return 0;
> }
>
> @@ -227,43 +206,6 @@ xfarray_element_is_null(
> return !memchr_inv(ptr, 0, array->obj_size);
> }
>
> -/*
> - * Store an element anywhere in the array that is unset. If there are no
> - * unset slots, append the element to the array.
> - */
> -int
> -xfarray_store_anywhere(
> - struct xfarray *array,
> - const void *ptr)
> -{
> - void *temp = xfarray_scratch(array);
> - loff_t endpos = xfarray_pos(array, array->nr);
> - loff_t pos;
> - int error;
> -
> - /* Find an unset slot to put it in. */
> - for (pos = 0;
> - pos < endpos && array->unset_slots > 0;
> - pos += array->obj_size) {
> - error = xfile_load(array->xfile, temp, array->obj_size,
> - pos);
> - if (error || !xfarray_element_is_null(array, temp))
> - continue;
> -
> - error = xfile_store(array->xfile, ptr, array->obj_size,
> - pos);
> - if (error)
> - return error;
> -
> - array->unset_slots--;
> - return 0;
> - }
> -
> - /* No unset slots found; attach it on the end. */
> - array->unset_slots = 0;
> - return xfarray_append(array, ptr);
> -}
> -
> /* Return length of array. */
> uint64_t
> xfarray_length(
> @@ -677,26 +619,10 @@ xfarray_qsort_pivot(
>
> /* Load the selected xfarray records into the pivot array. */
> for (i = 0; i < XFARRAY_QSORT_PIVOT_NR; i++) {
> - xfarray_idx_t idx;
> -
> recp = xfarray_pivot_array_rec(parray, pivot_rec_sz, i);
> idxp = xfarray_pivot_array_idx(parray, pivot_rec_sz, i);
>
> - /* No unset records; load directly into the array. */
> - if (likely(si->array->unset_slots == 0)) {
> - error = xfarray_sort_load(si, *idxp, recp);
> - if (error)
> - return error;
> - continue;
> - }
> -
> - /*
> - * Load non-null records into the scratchpad without changing
> - * the xfarray_idx_t in the pivot array.
> - */
> - idx = *idxp;
> - xfarray_sort_bump_loads(si);
> - error = xfarray_load_next(si->array, &idx, recp);
> + error = xfarray_sort_load(si, *idxp, recp);
> if (error)
> return error;
> }
>
>
next prev parent reply other threads:[~2026-09-22 18:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 6:13 [PATCHSET] xfs: LLM-inspired bug fixes, part 16 Darrick J. Wong
2026-09-21 6:15 ` [PATCH 01/14] xfs: fix missing xfs_qm_adjust_dqlimits call in quotacheck repair Darrick J. Wong
2026-09-22 5:14 ` Christoph Hellwig
2026-09-21 6:15 ` [PATCH 02/14] xfs: online quotacheck must dirty dquot if enforcement adjustments needed Darrick J. Wong
2026-09-22 5:14 ` Christoph Hellwig
2026-09-22 18:02 ` Darrick J. Wong
2026-09-21 6:15 ` [PATCH 03/14] xfs: fix buffer overruns in xfs_ioc_attr_list Darrick J. Wong
2026-09-22 5:15 ` Christoph Hellwig
2026-09-22 17:31 ` Darrick J. Wong
2026-09-21 6:16 ` [PATCH 04/14] xfs: clean up after failed metafile relinking Darrick J. Wong
2026-09-22 5:17 ` Christoph Hellwig
2026-09-22 17:33 ` Darrick J. Wong
2026-09-21 6:16 ` [PATCH 05/14] xfs: pass xfs_trans_resv object to reservation calculation helpers Darrick J. Wong
2026-09-22 5:18 ` Christoph Hellwig
2026-09-22 17:29 ` Darrick J. Wong
2026-09-22 17:34 ` Darrick J. Wong
2026-09-21 6:16 ` [PATCH 06/14] xfs: fix xfs_rename_space_res for non-pptr filesystems Darrick J. Wong
2026-09-22 5:20 ` Christoph Hellwig
2026-09-22 17:36 ` Darrick J. Wong
2026-09-21 6:16 ` [PATCH 07/14] xfs: fix ondisk symlink target validation in xrep_dinode_check_dfork Darrick J. Wong
2026-09-22 5:20 ` Christoph Hellwig
2026-09-22 20:42 ` Dave Chinner
2026-09-21 6:17 ` [PATCH 08/14] xfs: fix maximum atomic cow length computation Darrick J. Wong
2026-09-22 5:21 ` Christoph Hellwig
2026-09-22 6:53 ` Darrick J. Wong
2026-09-21 6:17 ` [PATCH 09/14] xfs: add missing healthmon trace strings Darrick J. Wong
2026-09-22 5:21 ` Christoph Hellwig
2026-09-21 6:17 ` [PATCH 10/14] xfarray: don't crash when sorting if array element crosses a folio Darrick J. Wong
2026-09-22 5:22 ` Christoph Hellwig
2026-09-22 17:53 ` Darrick J. Wong
2026-09-23 4:39 ` Christoph Hellwig
2026-09-21 6:17 ` [PATCH 11/14] xfarray: don't allow users to unset in the middle of an array Darrick J. Wong
2026-09-22 5:23 ` Christoph Hellwig
2026-09-22 6:47 ` Darrick J. Wong
2026-09-22 18:14 ` Darrick J. Wong [this message]
2026-09-21 6:18 ` [PATCH 12/14] xfs: don't allow sorting sparse arrays Darrick J. Wong
2026-09-22 5:24 ` Christoph Hellwig
2026-09-22 18:07 ` Darrick J. Wong
2026-09-21 6:18 ` [PATCH 13/14] xfs: simply the free space btree repair code Darrick J. Wong
2026-09-22 5:24 ` Christoph Hellwig
2026-09-21 6:18 ` [PATCH 14/14] xfarray: warn against sorting arrays with identical elements Darrick J. Wong
2026-09-22 5:25 ` Christoph Hellwig
2026-09-22 18:10 ` Darrick J. Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260922181433.GA2705364@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox