Linux Test Project
 help / color / mirror / Atom feed
From: Gang Yan <gang.yan@linux.dev>
To: ltp@lists.linux.it
Cc: Gang Yan <yangang@kylinos.cn>
Subject: [LTP] [PATCH 1/3] loongarch.in: add memfd_secret syscall
Date: Tue, 14 Jul 2026 18:14:52 +0800	[thread overview]
Message-ID: <20260714101454.8784-2-gang.yan@linux.dev> (raw)
In-Reply-To: <20260714101454.8784-1-gang.yan@linux.dev>

From: Gang Yan <yangang@kylinos.cn>

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:

'''
...
accept03.c:47: TFAIL: accept() on memfd secret expected ENOTSOCK: EBADF (9)
tst_fd.c:307: TBROK: close(38) failed: EBADF(9)
'''

This patch put it back, and the output is attached below:

'''
...
tst_fd.c: 262: TCONF: Skipping memfd secret : ENOSYS(38)
'''

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..3abc37552 100644
--- a/include/lapi/syscalls/loongarch64.in
+++ b/include/lapi/syscalls/loongarch64.in
@@ -296,6 +296,7 @@ mount_setattr 442
 quotactl_fd 443
 landlock_create_ruleset 444
 landlock_add_rule 445
+memfd_secret 447
 landlock_restrict_self 446
 process_mrelease 448
 futex_waitv 449
-- 
2.43.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-07-14 10:16 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 ` Gang Yan [this message]
2026-07-14 10:54   ` [LTP] loongarch.in: add memfd_secret syscall linuxtestproject.agent
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=20260714101454.8784-2-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