Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CA+G9fYtLoBo31wRD=+Q8DfO36OGBACp2GY6xvyj8CmUk37rbuA@mail.gmail.com>
 <20221108112811.56mhfrguuscrh2ow@wittgenstein>
In-Reply-To: <20221108112811.56mhfrguuscrh2ow@wittgenstein>
From:   Naresh Kamboju <naresh.kamboju@linaro.org>
Date:   Tue, 8 Nov 2022 18:01:33 +0530
Message-ID: <CA+G9fYsVnDSwudT=go0p__2Jas-JuT-8Y+9Jk1xPtA1h4Nmreg@mail.gmail.com>
Subject: Re: selftests: clone3: clone3_cap_checkpoint_restore fails - Could
 not set CAP_CHECKPOINT_RESTORE
To:     Christian Brauner <brauner@kernel.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>,
        Shuah Khan <shuah@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, 8 Nov 2022 at 16:58, Christian Brauner <brauner@kernel.org> wrote:
>
> 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?

These failures have been happening for a long time.

FYI,
LKFT email is configured to send out email to Linux next mailing list with
daily kselftest results / regressions / pass / fail / xfails / skips.

Please refer this link for our reports,
https://lore.kernel.org/linux-next/?q=lkft+kselftest+for+

We are improving our process to report failures and regressions on
mailing lists.

- Naresh