From: linuxtestproject.agent@gmail.com
To: Gang Yan <gang.yan@linux.dev>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] loongarch.in: add memfd_secret syscall
Date: Tue, 14 Jul 2026 10:54:28 +0000 [thread overview]
Message-ID: <20260714105429.4063-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260714101454.8784-2-gang.yan@linux.dev>
Hi Gang,
On Tue Jul 14 18:14:52 2026 +0800, Gang Yan wrote:
> loongarch.in: add memfd_secret syscall
--- [PATCH 1/3] ---
The subject names the wrong file. The changed file is "loongarch64.in",
not "loongarch.in".
> In 209f0c6360da('Update arch(s) syscalls files'), it only removes the
> 'memfd_secret' for loongarch, so that caused a error based on the old
> kernel:
"a error" -> "an error". Also, "based on the old kernel" is unclear: the
EBADF failure occurs because __NR_memfd_secret defaults to -1 when absent
from the syscall table, not because of any particular kernel version.
> +memfd_secret 447
> landlock_restrict_self 446
memfd_secret (447) is inserted before landlock_restrict_self (446),
breaking the ascending numerical order of the file. Should the insertion
point be after landlock_restrict_self?
landlock_add_rule 445
landlock_restrict_self 446
+ memfd_secret 447
process_mrelease 448
--- [PATCH 2/3] ---
The subject names the wrong file. The script is "generate_syscalls.sh"
(plural), not "generate_syscall.sh".
> +#define tst_syscall_base(NR, ...) ({ \
> + intptr_t tst_ret; \
> + if (NR == __LTP__NR_INVALID_SYSCALL) { \
> + errno = ENOSYS; \
> + tst_ret = -1; \
> + } else { \
> + tst_ret = syscall(NR, ##__VA_ARGS__); \
> + } \
> + tst_ret; \
> +})
The macro body uses spaces for indentation. LTP follows Linux kernel coding
style which requires tabs. The same applies to the refactored tst_syscall
body below.
> +#define tst_syscall(NR, ...) ({ \
> + intptr_t tst_ret = tst_syscall_base(NR, ##__VA_ARGS__); \
> + if (tst_ret == -1 && errno == ENOSYS) { \
> + TST_SYSCALL_BRK__(NR, #NR); \
> + } \
> + tst_ret; \
> +})
Same indentation issue -- tabs required.
--- [PATCH 3/3] ---
> If some feature is not supported by some arch, like _NR__memfd_secret,
Typo: "_NR__memfd_secret" should be "__NR_memfd_secret".
> This patch use tst_syscall to give a more specific fail reason:
The macro used throughout this patch is tst_syscall_base(), not
tst_syscall(). "use" -> "uses".
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-07-14 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 10:14 [LTP] [PATCH 0/3] tst_fd.c: fix test_failures on loongarch's old Gang Yan
2026-07-14 10:14 ` [LTP] [PATCH 1/3] loongarch.in: add memfd_secret syscall Gang Yan
2026-07-14 10:54 ` linuxtestproject.agent [this message]
2026-07-14 10:14 ` [LTP] [PATCH 2/3] generate_syscall.sh: add a helper named tst_syscall_base Gang Yan
2026-07-14 11:08 ` Andrea Cervesato via ltp
2026-07-14 10:14 ` [LTP] [PATCH 3/3] tst_fd.c: replace syscall() with tst_syscall_base() Gang Yan
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=20260714105429.4063-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=gang.yan@linux.dev \
--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.