selftests: clone3: clone3_clear_sighand failed - Bail out! Failed to clear signal handler for child process
selftests: clone3: clone3_clear_sighand failed on arm32 and i386 but passed on arm64 and x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
# selftests: clone3: clone3_clear_sighand # TAP version 13 # 1..1 # # clone3() syscall supported # Bail out! Failed to clear signal handler for child process # # Planned tests != run tests (1 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Test details links, https://lkft.validation.linaro.org/scheduler/job/5820146#L1795
Test results comparison link, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/tes...
metadata: git_ref: master git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next git_sha: b6fc3fddade7a194bd141a49f2689e50f796ef46 git_describe: next-20221108 kernel_version: 6.1.0-rc4 kernel-config: https://builds.tuxbuild.com/2HFnr3jvzSvcbeO3iSMp7Fbvmmq/config build-url: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/pipelines/688275399 artifact-location: https://builds.tuxbuild.com/2HFnr3jvzSvcbeO3iSMp7Fbvmmq toolchain: gcc-11
-- Linaro LKFT https://lkft.linaro.org
On Tue, Nov 08, 2022 at 03:28:55PM +0530, Naresh Kamboju wrote:
selftests: clone3: clone3_clear_sighand failed on arm32 and i386 but passed on arm64 and x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
# selftests: clone3: clone3_clear_sighand # TAP version 13 # 1..1 # # clone3() syscall supported # Bail out! Failed to clear signal handler for child process # # Planned tests != run tests (1 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Test details links, https://lkft.validation.linaro.org/scheduler/job/5820146#L1795
Test results comparison link, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/tes...
Seems before 27 September 2022 this test wasn't run on 32bit instances and noone ever noticed?
On Tue, 8 Nov 2022 at 15:34, Christian Brauner brauner@kernel.org wrote:
On Tue, Nov 08, 2022 at 03:28:55PM +0530, Naresh Kamboju wrote:
selftests: clone3: clone3_clear_sighand failed on arm32 and i386 but passed on arm64 and x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
# selftests: clone3: clone3_clear_sighand # TAP version 13 # 1..1 # # clone3() syscall supported # Bail out! Failed to clear signal handler for child process # # Planned tests != run tests (1 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Test details links, https://lkft.validation.linaro.org/scheduler/job/5820146#L1795
Test results comparison link, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/tes...
Seems before 27 September 2022 this test wasn't run on 32bit instances and noone ever noticed?
This email is about sharing the results log and reporting failures. If you think it is not supported on 32bit the test should SKIP instead of fail.
We have test data available from more than a year, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/tes...
- Naresh
On Tue, Nov 08, 2022 at 03:51:24PM +0530, Naresh Kamboju wrote:
On Tue, 8 Nov 2022 at 15:34, Christian Brauner brauner@kernel.org wrote:
On Tue, Nov 08, 2022 at 03:28:55PM +0530, Naresh Kamboju wrote:
selftests: clone3: clone3_clear_sighand failed on arm32 and i386 but passed on arm64 and x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
# selftests: clone3: clone3_clear_sighand # TAP version 13 # 1..1 # # clone3() syscall supported # Bail out! Failed to clear signal handler for child process # # Planned tests != run tests (1 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Test details links, https://lkft.validation.linaro.org/scheduler/job/5820146#L1795
Test results comparison link, https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/tes...
Seems before 27 September 2022 this test wasn't run on 32bit instances and noone ever noticed?
This email is about sharing the results log and reporting failures. If you think it is not supported on 32bit the test should SKIP instead of fail.
No, I was just asking whether this has been detected just now for the first time. If this has been a problem for such a long time I was just puzzled why this was never reported.
* Naresh Kamboju:
selftests: clone3: clone3_clear_sighand failed on arm32 and i386 but passed on arm64 and x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
# selftests: clone3: clone3_clear_sighand # TAP version 13 # 1..1 # # clone3() syscall supported # Bail out! Failed to clear signal handler for child process # # Planned tests != run tests (1 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Not sure why you are reporting this to libc-alpha. We'd like to help, but there doesn't seem to be anything glibc-specific in this report?
Thanks, Florian
On Tue, 8 Nov 2022 at 16:05, Florian Weimer fweimer@redhat.com wrote:
- Naresh Kamboju:
selftests: clone3: clone3_clear_sighand failed on arm32 and i386 but passed on arm64 and x86_64.
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
# selftests: clone3: clone3_clear_sighand # TAP version 13 # 1..1 # # clone3() syscall supported # Bail out! Failed to clear signal handler for child process # # Planned tests != run tests (1 != 0) # # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:0 error:0 not ok 2 selftests: clone3: clone3_clear_sighand # exit=1
Not sure why you are reporting this to libc-alpha. We'd like to help, but there doesn't seem to be anything glibc-specific in this report?
This is coming from a commit log having CC to the libc-alpha list. However, please ignore the report if it is not related.
-- tests: test CLONE_CLEAR_SIGHAND Test that CLONE_CLEAR_SIGHAND resets signal handlers to SIG_DFL for the child process and that CLONE_CLEAR_SIGHAND and CLONE_SIGHAND are mutually exclusive.
Cc: Florian Weimer fweimer@redhat.com Cc: libc-alpha@sourceware.org Cc: linux-api@vger.kernel.org Signed-off-by: Christian Brauner christian.brauner@ubuntu.com Link: https://lore.kernel.org/r/20191014104538.3096-2-christian.brauner@ubuntu.com
Thanks, Florian
- Naresh
-
Christian Brauner -
Florian Weimer -
Naresh Kamboju