From: linuxtestproject.agent@gmail.com
To: Wake Liu <wakel@google.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] tse_swap: Fill swapfile with zeroes on exFAT
Date: Tue, 10 Nov 2026 13:05:40 +0000 [thread overview]
Message-ID: <20261110130540.4085-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20261110112100.1594353-1-wakel@google.com>
Hi Wake,
On Tue Nov 10, 2026, Wake Liu wrote:
> tse_swap: Fill swapfile with zeroes on exFAT
> - /* Fill the file if needed (specific to old xfs filesystems) */
> - if (tst_fs_type(swapfile) == TST_XFS_MAGIC) {
> + /*
> + * Fill the file if needed: swapon() rejects preallocated but
> + * unwritten blocks on old XFS and on exFAT.
> + */
> + fs_type = tst_fs_type(swapfile);
> + if (fs_type == TST_XFS_MAGIC || fs_type == TST_EXFAT_MAGIC) {
> if (tst_fill_file(swapfile, 0, blk_size, blocks) != 0)
> tst_brk_(file, lineno, TBROK, "Failed to fill swapfile");
> }
The swapon() failure on fallocate()-preallocated exFAT swapfiles in v7.2 is a
kernel regression that was fixed in v7.4 by kernel commit 4483ab85d1e0
("exfat: map allocated extents for swap activation"), which suppresses
IOMAP_REPORT during swap activation so preallocated blocks beyond valid_size
are mapped as IOMAP_UNWRITTEN instead of IOMAP_HOLE. Filling the swapfile with
zeroes on exFAT works around this kernel bug in LTP and masks the failure on
kernels missing that fix, so this change should be dropped.
Verdict - Needs revision
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-11-10 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 11:21 [LTP] [PATCH] tse_swap: Fill swapfile with zeroes on exFAT Wake Liu via ltp
2026-11-10 13:05 ` linuxtestproject.agent [this message]
2026-11-11 6:18 ` Wake Liu via ltp
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=20261110130540.4085-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=wakel@google.com \
/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