mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaosheng Qu <chaosheng.qu.linux@gmail.com>
To: linux-trace-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Tomas Glozar <tglozar@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtla: add tests for tracefs instance cleanup
Date: Sun, 18 Oct 2026 11:50:20 +0800	[thread overview]
Message-ID: <179229542008.41291.4713973899027586435@gmail.com> (raw)
In-Reply-To: <sashiko-outbox-175505@kernel.org>

Thanks, the four points split into test-harness bugs and one test premise
that I over-claimed. The series is fixed locally; details below.

1. SKIP was swallowed

cleanup.t now emits a TAP "# SKIP" line when the helper logs SKIP, instead
of reporting a plain "ok". The helper also treats a missing tracefs, a
non-writable tracefs, or a missing CONFIG_OSNOISE_TRACER as SKIP rather
than a failure.

2. SIGINT race and leaked process

The repeated-interrupt case now waits for the tracefs instance to appear
before sending SIGINT, and verifies that it disappears after each run. The
SIGINT case also reaps the background rtla when the instance never
appeared. The helper is run under the suite timeout, so a stuck wait cannot
hang forever.

I also added SIGTERM to set_signals()/unset_signals() in common.c. Before
this, rtla only handled SIGINT and SIGALRM, so SIGTERM left the instance
behind. The test now checks that path instead of recording it as a known
issue.

3. Missing exit-code checks / action case

The self-timeout case now requires exit 0, and the action case requires exit
2 (the mismatched-action result). The action case uses -S, the stop-total
threshold, and skips if that threshold was not crossed. An idle machine may
not generate a sample above 1 us; that is a property of the workload, not a
cleanup result.

4. Unused TIMEOUT / reset_osnoise / dead code

run_cleanup_cases() now calls reset_osnoise and uses $TIMEOUT. The unused
check_instances_absent() helper is gone.

The series is based on 2f2f7eeef8b0a1a9b9ca998231419873ccae8d4e and is
commit 455d304ece2a938d0148a908c83f1774d4dbf298. I ran bash -n and
checkpatch.pl locally. The host has no writable tracefs, so the suite
reports SKIP here rather than a real pass.

The patch is attached.

Thanks,
Chaosheng

  parent reply	other threads:[~2026-10-18  3:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 12:23 Chaosheng Qu
     [not found] ` <sashiko-outbox-175505@kernel.org>
2026-10-18  3:50   ` Chaosheng Qu [this message]
2026-10-18  3:56 Chaosheng Qu

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=179229542008.41291.4713973899027586435@gmail.com \
    --to=chaosheng.qu.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglozar@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®