Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Muhammad Usama Anjum <usama.anjum@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Shuah Khan <shuah@kernel.org>,
	Andrey Konovalov <andreyknvl@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	Yeoreum Yun <yeoreum.yun@arm.com>,
	Mark Brown <broonie@kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:KERNEL SELFTEST FRAMEWORK"
	<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v3 1/4] selftests/arm64: Print missing MTE TAP headers
Date: Wed, 26 Aug 2026 09:25:35 +0100	[thread overview]
Message-ID: <fe6096b4-d906-4c1e-aeb3-7ca5cd164cab@arm.com> (raw)
In-Reply-To: <20260825111929.2882324-2-usama.anjum@arm.com>



On 25/08/2026 12:18, Muhammad Usama Anjum wrote:
> Most MTE tests set a TAP plan and emit results without first printing
> the TAP version header. Direct execution therefore starts with a plan
> such as "1..20" instead of "TAP version 13".
> 
> The problem is particularly visible in the GCR_EL1 context-switch test.
> It prints its plan before forking 1,024 child processes. When stdout is
> fully buffered, the plan remains in the stdio buffer. Each child inherits
> the pending "1..1" line and flushes its copy from exit(), producing
> repeated plan lines.
> 
> ksft_print_header() prints the TAP header and enables line buffering.
> Call it in every MTE test that is missing it. In the GCR_EL1 test, call
> it before the plan so the plan is flushed before the children are
> forked. In the remaining tests, call it before setup and prerequisite
> checks so early failures and whole-test skips also retain the header.
> 
> Fixes: 29f080881601 ("kselftest/arm64: check GCR_EL1 after context switch")
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@arm.com>

Reviewed-by: Vincenzo Frascino <vincenzo.frascino@arm.com>

...

  parent reply	other threads:[~2026-08-26  8:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 11:18 [PATCH v3 0/4] selftests/arm64: Fix MTE test setup and TAP reporting Muhammad Usama Anjum
2026-08-25 11:18 ` [PATCH v3 1/4] selftests/arm64: Print missing MTE TAP headers Muhammad Usama Anjum
2026-08-25 13:58   ` Mark Brown
2026-08-26  8:25   ` Vincenzo Frascino [this message]
2026-08-25 11:18 ` [PATCH v3 2/4] selftests/arm64: Treat KSM merge_across_nodes as optional Muhammad Usama Anjum
2026-08-25 14:00   ` Mark Brown
2026-08-26  8:26   ` Vincenzo Frascino
2026-08-25 11:18 ` [PATCH v3 3/4] selftests/arm64: Fix MTE prctl TAP plan Muhammad Usama Anjum
2026-08-26  8:27   ` Vincenzo Frascino
2026-08-25 11:18 ` [PATCH v3 4/4] selftests/arm64: Add MTE test config fragment Muhammad Usama Anjum
2026-08-26  8:27   ` Vincenzo Frascino
2026-08-27 15:22 ` [PATCH v3 0/4] selftests/arm64: Fix MTE test setup and TAP reporting Will Deacon

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=fe6096b4-d906-4c1e-aeb3-7ca5cd164cab@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=amit.kachhap@arm.com \
    --cc=andreyknvl@gmail.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@arm.com \
    --cc=will@kernel.org \
    --cc=yeoreum.yun@arm.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