From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <martin.wilck@suse.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
Brian Bunker <brian@purestorage.com>,
dm-devel@lists.linux.dev, Martin Wilck <mwilck@suse.com>
Subject: Re: [PATCH v2 3/5] multipath-tools tests: add test program for thread runners
Date: Mon, 27 Apr 2026 20:24:30 -0400 [thread overview]
Message-ID: <ae_-PpInT2ZT4yBC@redhat.com> (raw)
In-Reply-To: <20260423204446.472642-4-mwilck@suse.com>
On Thu, Apr 23, 2026 at 10:44:44PM +0200, Martin Wilck wrote:
> Add a test program for the "runner" thread implementation from the previous
> commit. The test program runs simulated "hanging" threads that may time
> out, and optionally kills all threads at an arbitrary point in time. See
> the comments at the top of the file for details.
>
> Also add a test driver script (runner-test.sh) with a few reasonable
> combinations of command line arguments.
>
> The test program has been used to test the "runner" implementation
> extensively on different architectures (x86_64, aarch64, ppc64le, s390x),
> using both valgrind and the gcc address sanitizer (libasan) for detection
> of memory leaks and use-after-free errors.
>
> For valgrind, a suppression file needs to be added, as valgrind doesn't
> seem to capture the deallocation of thread local storage for detached
> threads in the test case where the test program is killed. The suppression
> affects only memory allocated by glibc. This leak has not been seen with
> libasan, only with valgrind.
>
> Signed-off-by: Martin Wilck <mwilck@suse.com>
Reviewed-by: Benjamin Marzinski <bmarzins@redhat.com>
next prev parent reply other threads:[~2026-04-28 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 20:44 [PATCH v2 0/5] multipath-tools: generic async threads for TUR checker Martin Wilck
2026-04-23 20:44 ` [PATCH v2 1/5] multipathd: get_new_state: map PATH_TIMEOUT to PATH_DOWN Martin Wilck
2026-04-23 20:44 ` [PATCH v2 2/5] libmpathutil: add generic implementation for checker thread runners Martin Wilck
2026-04-28 0:20 ` Benjamin Marzinski
2026-04-28 10:47 ` Martin Wilck
2026-04-23 20:44 ` [PATCH v2 3/5] multipath-tools tests: add test program for " Martin Wilck
2026-04-28 0:24 ` Benjamin Marzinski [this message]
2026-04-23 20:44 ` [PATCH v2 4/5] libmultipath: TUR checker: use runner threads Martin Wilck
2026-04-28 4:04 ` Benjamin Marzinski
2026-04-23 20:44 ` [PATCH v2 5/5] libmultipath: tur checker: improve tur_deep_sleep() test Martin Wilck
2026-04-28 4:05 ` Benjamin Marzinski
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=ae_-PpInT2ZT4yBC@redhat.com \
--to=bmarzins@redhat.com \
--cc=brian@purestorage.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
--cc=martin.wilck@suse.com \
--cc=mwilck@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.