From: Cyril Hrubis <chrubis@suse.cz>
To: "Ricardo B. Marlière" <rbm@suse.com>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v6 3/3] syscalls/modify_ldt01: Refactor into new API
Date: Mon, 7 Apr 2025 14:41:23 +0200 [thread overview]
Message-ID: <Z_PH8xBBsESE4K8I@yuki.lan> (raw)
In-Reply-To: <20250402-conversions-modify_ldt-v6-3-2e4b0e27870e@suse.com>
Hi!
> Now that we're using the wrapped modify_ldt() from the lapi/ldt.h which
> uses tst_syscall(), it does not make sense to keep the first block of the
> original test which simply checked for ENOSYS. Also, merge modify_ldt03
> into modify_ldt01 and extend the test to cover all the errors from the
> manual page.
>
> Signed-off-by: Ricardo B. Marlière <rbm@suse.com>
> ---
> testcases/kernel/syscalls/modify_ldt/.gitignore | 5 +-
> .../kernel/syscalls/modify_ldt/modify_ldt01.c | 264 +++++----------------
> .../kernel/syscalls/modify_ldt/modify_ldt03.c | 105 --------
You should remove modify_ldt03 from the syscalls runtest file as well.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2025-04-07 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 9:58 [LTP] [PATCH v6 0/3] syscalls/modify_ldt: Refactor into new API Ricardo B. Marlière via ltp
2025-04-02 9:58 ` [LTP] [PATCH v6 1/3] syscalls/modify_ldt: Add lapi/ldt.h Ricardo B. Marlière via ltp
2025-04-07 12:09 ` Cyril Hrubis
2025-04-07 12:18 ` Ricardo B. Marli��re via ltp
2025-04-02 9:58 ` [LTP] [PATCH v6 2/3] syscalls/modify_ldt02: Refactor into new API Ricardo B. Marlière via ltp
2025-04-07 12:24 ` Cyril Hrubis
2025-04-02 9:58 ` [LTP] [PATCH v6 3/3] syscalls/modify_ldt01: " Ricardo B. Marlière via ltp
2025-04-07 12:41 ` Cyril Hrubis [this message]
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=Z_PH8xBBsESE4K8I@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rbm@suse.com \
/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.