From: Gang Yan <gang.yan@linux.dev>
To: ltp@lists.linux.it
Cc: Gang Yan <yangang@kylinos.cn>
Subject: [LTP] [PATCH v2] loongarch64.in: add memfd_secret syscall
Date: Wed, 15 Jul 2026 15:58:50 +0800 [thread overview]
Message-ID: <20260715075850.66118-1-gang.yan@linux.dev> (raw)
From: Gang Yan <yangang@kylinos.cn>
memfd_secret(447) is already supported on newer LoongArch kernels, but
the loongarch64.in was missing its definition. This caused tests using
memfd_secret (e.g. accept03, readahead01, splice07 via tst_fd.c) to
incorrectly skip with TCONF even when the kernel supports it:
'''
accept03.c:46: TPASS: accept() on memfd: ENOTSOCK (88)
tst_fd.c:261: TCONF: Skipping memfd secret : ENOSYS (38)
'''
This patch adds memfd_secret(447) so these tests can run normally:
'''
accept03.c:46: TPASS: accept() on memfd secret : ENOTSOCK (88)
'''
Signed-off-by: Gang Yan <yangang@kylinos.cn>
---
include/lapi/syscalls/loongarch64.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/lapi/syscalls/loongarch64.in b/include/lapi/syscalls/loongarch64.in
index 5407b86ea..a1dfce79e 100644
--- a/include/lapi/syscalls/loongarch64.in
+++ b/include/lapi/syscalls/loongarch64.in
@@ -297,6 +297,7 @@ quotactl_fd 443
landlock_create_ruleset 444
landlock_add_rule 445
landlock_restrict_self 446
+memfd_secret 447
process_mrelease 448
futex_waitv 449
set_mempolicy_home_node 450
--
2.43.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-07-15 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 7:58 Gang Yan [this message]
2026-07-15 8:06 ` [LTP] [PATCH v2] loongarch64.in: add memfd_secret syscall Andrea Cervesato via ltp
2026-07-15 10:53 ` [LTP] " linuxtestproject.agent
2026-07-15 11:29 ` [LTP] [PATCH v2] " Andrea Cervesato 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=20260715075850.66118-1-gang.yan@linux.dev \
--to=gang.yan@linux.dev \
--cc=ltp@lists.linux.it \
--cc=yangang@kylinos.cn \
/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