From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Cyril Hrubis" <chrubis@suse.cz>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 2/5] Add listns fallback header
Date: Fri, 20 Mar 2026 13:34:05 +0000 [thread overview]
Message-ID: <69bd4cce.df0a0220.1f9b07.885e@mx.google.com> (raw)
In-Reply-To: <ab0i-cmCvbuJc8dv@yuki.lan>
Hi!
> Hi!
> > +static inline int listns(struct listns_req *req, uint64_t *ns_ids,
> > + size_t nr_ns_ids, unsigned int flags)
> > +{
> > + return tst_syscall(__NR_listns, req, ns_ids, nr_ns_ids, flags);
> > +}
>
> Do we need a configure check in a case that glibc happens to eventually
> add listns() syscall?
>
Does it make sense at this stage?
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-03-20 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 11:48 [LTP] [PATCH v2 0/5] listns() testing suite Andrea Cervesato
2026-03-13 11:48 ` [LTP] [PATCH v2 1/5] Update architectures syscalls identifiers Andrea Cervesato
2026-03-20 10:28 ` Cyril Hrubis
2026-03-20 13:21 ` Andrea Cervesato via ltp
2026-03-13 11:48 ` [LTP] [PATCH v2 2/5] Add listns fallback header Andrea Cervesato
2026-03-20 10:35 ` Cyril Hrubis
2026-03-20 13:34 ` Andrea Cervesato via ltp [this message]
2026-03-23 10:16 ` Cyril Hrubis
2026-03-24 14:49 ` Andrea Cervesato via ltp
2026-03-13 11:48 ` [LTP] [PATCH v2 3/5] Add NS_GET_ID fallback Andrea Cervesato
2026-03-20 10:36 ` Cyril Hrubis
2026-03-13 11:48 ` [LTP] [PATCH v2 4/5] syscalls: add listns01 test for EFAULT on invalid address Andrea Cervesato
2026-03-20 10:39 ` Cyril Hrubis
2026-03-13 11:48 ` [LTP] [PATCH v2 5/5] syscalls: add listns02 functionality test Andrea Cervesato
2026-03-20 11:19 ` Cyril Hrubis
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=69bd4cce.df0a0220.1f9b07.885e@mx.google.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=chrubis@suse.cz \
/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