From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] fallocate01: Convert to new API
Date: Fri, 7 Aug 2026 10:03:58 +0000 [thread overview]
Message-ID: <20260807100358.4121-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260807-convert_fallocate_suite-v2-1-3761f7b74b1f@suse.com>
Hi Andrea,
On Fri, 7 Aug 2026, Andrea Cervesato wrote:
> fallocate01: Convert to new API
--- [PATCH 1/2] ---
> Convert the fallocate01 test case from the legacy LTP API (test.h) to the
> new tst_test API using a table-driven struct tcase[] and TST_EXP_* macros.
Could the commit body explain why this nontrivial API conversion is needed?
It currently only restates what was converted and how.
--- [PATCH 2/2] ---
> TEST(fallocate(fdw, FALLOC_FL_KEEP_SIZE, 0, BLOCK_SIZE));
> if (TST_RET == -1 && (TST_ERR == EOPNOTSUPP || TST_ERR == ENOSYS))
> tst_brk(TCONF, "fallocate() not supported");
Could the filesystem support probe be removed, or availability handling be
restricted to ENOSYS?
Linux 7.2 validates the read-only descriptor, invalid offset and length, and
offset-plus-length overflow before consulting file->f_op->fallocate. These
error cases therefore remain valid when the backing filesystem returns
EOPNOTSUPP for a valid allocation. The new probe skips that coverage, unlike
the legacy test.
> Convert the fallocate02 test case from the legacy LTP API (test.h) to the
> new tst_test API using a table-driven struct tcase[] and TST_EXP_FAIL for
> each error-path oracle.
Could the commit body explain why this nontrivial API conversion is needed?
It currently only restates what was converted and how.
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-08-07 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:15 [LTP] [PATCH v2 0/2] Convert fallocate testing suite Andrea Cervesato
2026-08-07 8:15 ` [LTP] [PATCH v2 1/2] fallocate01: Convert to new API Andrea Cervesato
2026-08-07 10:03 ` linuxtestproject.agent [this message]
2026-08-07 8:15 ` [LTP] [PATCH v2 2/2] fallocate02: " Andrea Cervesato
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 11:48 [LTP] [PATCH 1/2] fallocate01: " Andrea Cervesato
2026-07-20 13:16 ` [LTP] " linuxtestproject.agent
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=20260807100358.4121-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.