From: Martin Doucha <mdoucha@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/4] Improve reliability of ioctl_sg01
Date: Tue, 25 Aug 2020 18:07:31 +0200 [thread overview]
Message-ID: <20200825160735.24602-1-mdoucha@suse.cz> (raw)
ioctl_sg01 needs dirty memory to reliably detect kernel data leaks. Its
description originally recommended running it after mem01 which has been
recently dropped.
Add helper function to LTP library for pre-polluting free memory and loop
the main check in ioctl_sg01 to further decrease the chance of false negative.
Martin Doucha (4):
Add SAFE_SYSINFO() macro
Add tst_pollute_memory() helper function
ioctl_sg01: Pollute free memory in setup
ioctl_sg01: Loop data leak check 100 times
include/tst_memutils.h | 22 +++++++
include/tst_safe_macros.h | 5 ++
lib/safe_macros.c | 20 +++++++
lib/tst_memutils.c | 62 ++++++++++++++++++++
testcases/kernel/syscalls/ioctl/ioctl_sg01.c | 32 ++++++----
5 files changed, 128 insertions(+), 13 deletions(-)
create mode 100644 include/tst_memutils.h
create mode 100644 lib/tst_memutils.c
--
2.28.0
next reply other threads:[~2020-08-25 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 16:07 Martin Doucha [this message]
2020-08-25 16:07 ` [LTP] [PATCH v2 1/4] Add SAFE_SYSINFO() macro Martin Doucha
2020-09-02 11:39 ` Petr Vorel
2020-08-25 16:07 ` [LTP] [PATCH v2 2/4] Add tst_pollute_memory() helper function Martin Doucha
2020-09-02 17:05 ` Petr Vorel
2020-08-25 16:07 ` [LTP] [PATCH v2 3/4] ioctl_sg01: Pollute free memory in setup Martin Doucha
2020-09-02 17:13 ` Petr Vorel
2020-08-25 16:07 ` [LTP] [PATCH v2 4/4] ioctl_sg01: Loop data leak check 100 times Martin Doucha
2020-09-02 17:17 ` Petr Vorel
2020-09-03 13:19 ` Martin Doucha
2020-09-03 14:03 ` Petr Vorel
2020-09-03 14:22 ` [LTP] [PATCH v2 0/4] Improve reliability of ioctl_sg01 Petr Vorel
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=20200825160735.24602-1-mdoucha@suse.cz \
--to=mdoucha@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.