On Thu, 3 Mar 2022 19:28:17 +0000, Mark Brown wrote: > If the test triggers a problem it may well result in a log message from > the kernel such as a WARN() or BUG(). If these include a PID it can help > with debugging to know if it was the parent or child process that triggered > the issue, since the test is just creating a new thread the process name > will be the same either way. Print the PIDs of the parent and child on > startup so users have this information to hand should it be needed. > > [...] Applied to arm64 (for-next/kselftest), thanks! [1/1] kselftest/arm64: Log the PIDs of the parent and child in sve-ptrace https://git.kernel.org/arm64/c/e2dc49ef6c6b Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev