linux-kernel - Re: selftests: clone3: clone3_clear_sighand failed - Bail out! Failed to clear signal handler for child process

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20221108112500.rffm2hmt2kvdc3io@wittgenstein>
Date:   Tue, 8 Nov 2022 12:25:00 +0100
From:   Christian Brauner <brauner@...nel.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, Florian Weimer <fweimer@...hat.com>,
        libc-alpha@...rceware.org, linux-api@...r.kernel.org,
        Christian Brauner <christian.brauner@...ntu.com>,
        Shuah Khan <shuah@...nel.org>
Subject: Re: selftests: clone3: clone3_clear_sighand failed - Bail out!
 Failed to clear signal handler for child process

On Tue, Nov 08, 2022 at 03:51:24PM +0530, Naresh Kamboju wrote:
> On Tue, 8 Nov 2022 at 15:34, Christian Brauner <brauner@...nel.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@...aro.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/testrun/12848543/suite/kselftest-clone3/test/clone3.clone3_clear_sighand/history/
> >
> > 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.