diff options
| author | Mark Brown <[email protected]> | 2022-03-03 19:28:17 +0000 |
|---|---|---|
| committer | Will Deacon <[email protected]> | 2022-03-07 21:46:57 +0000 |
| commit | e2dc49ef6c6b0e76c6d37cbec1161662570044e7 (patch) | |
| tree | 372273bc947bef8f526b1a242f587254d52de3a3 /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 32de73e89099c3f243032a733d3a64d417327a70 (diff) | |
kselftest/arm64: Log the PIDs of the parent and child in sve-ptrace
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.
Signed-off-by: Mark Brown <[email protected]>
Reviewed-by: Shuah Khan <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Will Deacon <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions