From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/2] metaparse: Add shell test parser
Date: Wed, 12 Feb 2025 15:03:40 +0100 [thread overview]
Message-ID: <20250212140340.GA2054076@pevik> (raw)
In-Reply-To: <20250212131618.6810-2-chrubis@suse.cz>
Hi Cyril,
Great, thank you!
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Quick notes:
* Implementing help under -h would be a bonus (it segfaults on -h, metadata.c
has it). But this should not block you merging it.
* Please merge with whitespace error
$ make check-metaparse-sh
CHECK metadata/metaparse-sh.c
metaparse-sh.c:90: ERROR: code indent should use tabs where possible
* Resulting JSON has true, 1 instead would be nice. Again, tiny detail.
"vma05.sh": {
"doc": [
"",
"[Description]",
"",
"Regression test if the vsyscall and vdso VMA regions are reported correctly.",
"",
"While [vsyscall] is mostly deprecated with newer systems, there is",
"still plenty of kernels compiled with CONFIG_LEGACY_VSYSCALL_NATIVE and",
"CONFIG_LEGACY_VSYSCALL_EMULATE (see linux/arch/x86/Kconfig for option",
"descriptions). First part of the test will check eligible kernels for",
"regression for a bug fixed by commit 103efcd9aac1 (fix perms/range of",
"vsyscall vma in /proc/*/maps).",
"",
"Second part of test checks [vdso] VMA permissions (fixed with commits",
"b6558c4a2378 (fix [vdso] page permissions) and e5b97dde514f (Add",
"VM_ALWAYSDUMP)). As a consequence of this bug, VMAs were not included",
"in core dumps which resulted in eg. incomplete backtraces and invalid",
"core dump files created by gdb."
],
"needs_root": true,
"needs_tmpdir": true,
"needs_cmds": ["gdb", "uname"],
"save_restore": [
["/proc/sys/kernel/core_pattern", "core", "TBROK"],
["/proc/sys/kernel/core_uses_pid", "0", "TBROK"]
],
"tags": [
["linux-git", "103efcd9aac1"],
["linux-git", "b6558c4a2378"],
["linux-git", "e5b97dde514f"]
],
"fname": "testcases/kernel/mem/vma/vma05.sh"
}
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-02-12 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 13:16 [LTP] [PATCH 0/2] Add shell test metadata parser Cyril Hrubis
2025-02-12 13:16 ` [LTP] [PATCH 1/2] metaparse: Add shell test parser Cyril Hrubis
2025-02-12 14:03 ` Petr Vorel [this message]
2025-02-13 12:48 ` Ricardo B. Marlière
2025-02-12 13:16 ` [LTP] [PATCH 2/2] metaparse: data_storage: Fix warning Cyril Hrubis
2025-02-12 14:04 ` Petr Vorel
2025-02-13 12:41 ` [LTP] [PATCH 0/2] Add shell test metadata parser Ricardo B. Marlière
2025-02-13 14:06 ` Cyril Hrubis
2025-02-25 13:14 ` 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=20250212140340.GA2054076@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--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 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.