linux-kernel - Re: selftests: clone3: clone3_cap_checkpoint_restore fails

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221108112811.56mhfrguuscrh2ow@wittgenstein>
Date:   Tue, 8 Nov 2022 12:28:11 +0100
From:   Christian Brauner <brauner@...nel.org>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     open list <linux-kernel@...r.kernel.org>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>, lkft-triage@...ts.linaro.org,
        Florian Weimer <fweimer@...hat.com>, libc-alpha@...rceware.org,
        linux-api@...r.kernel.org, Shuah Khan <shuah@...nel.org>
Subject: Re: selftests: clone3: clone3_cap_checkpoint_restore fails - Could
 not set CAP_CHECKPOINT_RESTORE

On Tue, Nov 08, 2022 at 03:59:56PM +0530, Naresh Kamboju wrote:
> selftests clone3 cap_checkpoint_restore fails on all devices.
> 
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> 
> [   97.198602] audit: type=1701 audit(1651167820.383:12):
> auid=4294967295 uid=0 gid=0 ses=4294967295 pid=1732
> comm=\"clone3_cap_chec\"
> exe=\"/opt/kselftests/default-in-kernel/clone3/clone3_cap_checkpoint_restore\"
> sig=6 res=1
> 
> # selftests: clone3: clone3_cap_checkpoint_restore
> # TAP version 13
> # 1..1
> # # Starting 1 tests from 1 test cases.
> # #  RUN           global.clone3_cap_checkpoint_restore ...
> # # clone3_cap_checkpoint_restore.c:155:clone3_cap_checkpoint_restore:Child
> has PID 1733
> # # clone3() syscall supported
> # cap_set_proc: Operation not permitted
> # # clone3_cap_checkpoint_restore.c:164:clone3_cap_checkpoint_restore:Expected
> set_capability() (-1) == 0 (0)
> # # clone3_cap_checkpoint_restore.c:165:clone3_cap_checkpoint_restore:Could
> not set CAP_CHECKPOINT_RESTORE
> # # clone3_cap_checkpoint_restore: Test terminated by assertion
> # #          FAIL  global.clone3_cap_checkpoint_restore
> # not ok 1 global.clone3_cap_checkpoint_restore
> # # FAILED: 0 / 1 tests passed.
> # # Totals: pass:0 fail:1 xfail:0 xpass:0 skip:0 error:0
> not ok 4 selftests: clone3: clone3_cap_checkpoint_restore # exit=1
> 
> Test details links,
> https://lkft.validation.linaro.org/scheduler/job/5812724#L2074
> 
> Test results comparison link,
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/testrun/12848543/suite/kselftest-clone3/tests/
> 
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/testrun/12848543/suite/kselftest-clone3/test/clone3.clone3_cap_checkpoint_restore/history/
> 
> https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20221107/testrun/12848543/suite/kselftest-clone3/test/clone3.clone3_cap_checkpoint_restore/details/

Similar question to the other report. Is this something that has
happened before or are we starting to see this failures just now?