From: Christian Brauner <brauner@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
lkft-triage@lists.linaro.org, Florian Weimer <fweimer@redhat.com>,
libc-alpha@sourceware.org, linux-api@vger.kernel.org,
Shuah Khan <shuah@kernel.org>
Subject: Re: selftests: clone3: clone3_cap_checkpoint_restore fails - Could not set CAP_CHECKPOINT_RESTORE
Date: Tue, 8 Nov 2022 12:28:11 +0100 [thread overview]
Message-ID: <20221108112811.56mhfrguuscrh2ow@wittgenstein> (raw)
In-Reply-To: <CA+G9fYtLoBo31wRD=+Q8DfO36OGBACp2GY6xvyj8CmUk37rbuA@mail.gmail.com>
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@linaro.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?
prev parent reply other threads:[~2022-11-08 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 10:29 selftests: clone3: clone3_cap_checkpoint_restore fails - Could not set CAP_CHECKPOINT_RESTORE Naresh Kamboju
2022-11-08 11:28 ` Christian Brauner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221108112811.56mhfrguuscrh2ow@wittgenstein \
--to=brauner@kernel.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).