Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] doc: update more syscalls stats
Date: Tue, 30 Jul 2024 09:41:47 +0200	[thread overview]
Message-ID: <20240730074147.GB1327610@pevik> (raw)
In-Reply-To: <20240426120051.21806-1-andrea.cervesato@suse.de>

> From: Andrea Cervesato <andrea.cervesato@suse.com>

> Some more syscalls are already tested in LTP, but they are part of
> different testing suites. For example, seccomp() is tested in prctl()
> testing suite. Some other syscalls need to be blacklisted, since they
> are part of MIPS or internal kernel usage.

> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
>  doc/conf.py | 4 ++++
>  1 file changed, 4 insertions(+)

> diff --git a/doc/conf.py b/doc/conf.py
> index d0f185b28..b54e0e60d 100644
> --- a/doc/conf.py
> +++ b/doc/conf.py
> @@ -83,6 +83,8 @@ def generate_syscalls_stats(_):
>          'getpmsg',
>          'putmsg',
>          'putpmsg',
> +        'seccomp',
> +        'semtimedop',
I guess there are more to add, right?
At least cachestat and landlock.
Could you please add them before you merge?

Reviewed-by: Petr Vorel <pvorel@suse.cz>

Also it'd be nice to have the lists sorted.

Kind regards,
Petr

>      ]

>      # populate with not implemented, reserved, unmaintained syscalls defined
> @@ -101,6 +103,8 @@ def generate_syscalls_stats(_):
>          'sysmips',
>          'mq_getsetattr',
>          'vserver',
> +        'cachectl',
> +        'restart_syscall',
>      ]

>      # fetch syscalls file

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

  reply	other threads:[~2024-07-30  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26 12:00 [LTP] [PATCH v1] doc: update more syscalls stats Andrea Cervesato
2024-07-30  7:41 ` Petr Vorel [this message]
2024-09-03  6:47   ` 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=20240730074147.GB1327610@pevik \
    --to=pvorel@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox