Re: [main-line][PowerPC]selftests/powerpc/signal: sigfuz fails
From: Madhavan Srinivasan
Date: Tue Mar 18 2025 - 06:50:59 EST
On 3/17/25 4:43 PM, Michael Ellerman wrote:
> Venkat Rao Bagalkote <venkat88@xxxxxxxxxxxxx> writes:
>> Greetings!!
>>
>> I am observing selftests/powerpc/signal:sigfuz test fails on linux
>> mainline repo on IBM Power10 systems.
>>
>> The test passes on the kernel with commit head:
>> 619f0b6fad524f08d493a98d55bac9ab8895e3a6 and fails on the kernel with
>> commit head: ce69b4019001407f9cd738dd2ba217b3a8ab831b on the main line.
>>
>>
>> Repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>
>> I tried to do git bisect and the bisect tool pointed first bad commit
>> to: 16ebb6f5b6295c9688749862a39a4889c56227f8.
>>
>> But upon reverting the first bad commit issue is still seen. So please
>> ignore, if the bisection dosent help.
>>
>>
>> Error:
>>
>> # selftests: powerpc/signal: sigfuz
>> # test: signal_fuzzer
>> # tags: git_version:v6.14-rc7-1-g49c747976afa
>> # !! killing signal_fuzzer
>> # !! child died by signal 15
>> # failure: signal_fuzzer
>> not ok 3 selftests: powerpc/signal: sigfuz # exit=1
>
> That error means the test is timing out and being killed by the test
> harness.
>
I tired multiple times with the config shared by Venkat in my P10 LPAR
and it always passes for me with default timeout as 0.
ok 2 selftests: powerpc/signal: signal_tm
# timeout set to 0
# selftests: powerpc/signal: sigfuz
# test: signal_fuzzer
# tags: git_version:v6.14-rc2-61-g861efb8a48ee
# success: signal_fuzzer
ok 3 selftests: powerpc/signal: sigfuz
# timeout set to 0
# selftests: powerpc/signal: sigreturn_vdso
# test: sigreturn_vdso
# tags: git_version:v6.14-rc2-61-g861efb8a48ee
# VDSO is at 0x7fff9aac0000-0x7fff9aacffff (65536 bytes)
# Signal delivered OK with VDSO mapped
# VDSO moved to 0x7fff9aa50000-0x7fff9aa5ffff (65536 bytes)
# Signal delivered OK with VDSO moved
# Unmapped VDSO
# Remapped the stack executable
# Signal delivered OK with VDSO unmapped
# success: sigreturn_vdso
Setup: P10 LPAR with 16CPUs, LPAR running only the selftest
Kernel: powerpc/next (861efb8a48ee), config shared by venkat
Maddy
> That could be due to a bug, but it could just be that your system is
> overloaded or something. You can increase the timeout in the code by
> adding a call to test_harness_timeout().
>
> The test also includes lots of randomisation, so if you actually need to
> bisect it you'd want to change the code to use a consistent random seed
> in the calls to srand().
>
> cheers