From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it, chrubis@suse.cz, pvorel@suse.cz
Subject: [LTP] [PATCH v2 0/3] provide a unified way to parse /proc/cmdline
Date: Sat, 9 Mar 2024 17:01:10 +0800 [thread overview]
Message-ID: <20240309090113.3121235-1-liwang@redhat.com> (raw)
V1 --> V2
* redefine the struct name to tst_kcmdline_var
* make use of SAFE_FOPEN/FCLOSE macro (Petr)
* read the file char char building up the key and value (Cyril)
* remove redundant varibales from the test (Petr)
Li Wang (3):
kconfig: add funtion to parse /proc/cmdline
init_module: To handle kernel module signature enforcement
stack_clash: make use of tst_kcmdline_parse
include/tst_kconfig.h | 23 ++++++++++
lib/tst_kconfig.c | 45 +++++++++++++++++++
testcases/cve/stack_clash.c | 14 +++---
.../syscalls/delete_module/delete_module01.c | 8 ++++
.../syscalls/delete_module/delete_module03.c | 8 ++++
.../syscalls/finit_module/finit_module01.c | 15 ++++++-
.../syscalls/finit_module/finit_module02.c | 37 +++++++++------
.../syscalls/init_module/init_module01.c | 13 ++++++
.../syscalls/init_module/init_module02.c | 19 +++++++-
9 files changed, 158 insertions(+), 24 deletions(-)
--
2.40.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2024-03-09 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 9:01 Li Wang [this message]
2024-03-09 9:01 ` [LTP] [PATCH v2 1/3] kconfig: add funtion to parse /proc/cmdline Li Wang
2024-03-11 12:27 ` Petr Vorel
2024-03-09 9:01 ` [LTP] [PATCH v2 2/3] init_module: To handle kernel module signature enforcement Li Wang
2024-03-09 9:01 ` [LTP] [PATCH v2 3/3] stack_clash: make use of tst_kcmdline_parse Li Wang
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=20240309090113.3121235-1-liwang@redhat.com \
--to=liwang@redhat.com \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=pvorel@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 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.