linux-kernel - Re: LTP: list of failures on 32bit and compat mode

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: <CA+G9fYtvp+iu-hA0YnMuT9gVET+4VFuz7faGTUWfmY_=dPtzZg@mail.gmail.com>
Date:   Tue, 11 Apr 2023 23:07:02 +0530
From:   Naresh Kamboju <naresh.kamboju@...aro.org>
To:     Petr Vorel <pvorel@...e.cz>
Cc:     Arnd Bergmann <arnd@...db.de>,
        open list <linux-kernel@...r.kernel.org>,
        LTP List <ltp@...ts.linux.it>, llvm@...ts.linux.dev,
        chrubis <chrubis@...e.cz>, Nathan Chancellor <nathan@...nel.org>,
        Anders Roxell <anders.roxell@...aro.org>,
        Daniel Díaz <daniel.diaz@...aro.org>,
        Benjamin Copeland <ben.copeland@...aro.org>,
        Tudor Cretu <tudor.cretu@....com>
Subject: Re: LTP: list of failures on 32bit and compat mode

On Tue, 11 Apr 2023 at 22:15, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
>
> On Thu, 6 Apr 2023 at 16:26, Petr Vorel <pvorel@...e.cz> wrote:
> >
> > > On Thu, Apr 6, 2023, at 11:11, Naresh Kamboju wrote:
> > > > Following LTP syscalls failed on the i386 and arm environments with
> > > > Linux next / mainline kernels. The userspace is coming from Open
> > > > Embedded kirkstone.

<Trim>
> > testcases/kernel/syscalls/fstatfs/fstatfs02.c was converted to new LTP API in
> > 5a8f89d35 ("syscalls/statfs02, fstatfs02: Convert to new API"), which was
> > released in 20220930. There is already newer release 20230127.
> > Generally it's safer to test mainline kernel with LTP master,
> > but this fix has already been in the latest LTP release 20230127.
> > And this error has been later fixed with
> > 492542072 ("syscalls/statfs02, fstatfs02: Accept segfault instead of EFAULT")
>
> Thanks for insite about the failed test investigations.
>
> >
> > @Naresh which LTP do you use for testing? It must be some older LTP :(.
>
> Our build system started running LTP version 20230127.
> I will keep you posted with the latest findings.

Few quick updates,
Do you see these failures on compat mode ?

Following regressions noticed with LTP version 20230127 on Linux next.

Regressions found on juno-r2-compat:
Regressions found on qemu_arm64-compat:

  ltp-syscalls/fcntl34
  ltp-syscalls/fcntl36
  ltp-syscalls/fcntl34_64
  ltp-syscalls/fcntl36_64

tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
fcntl34.c:87: TINFO: write to a file inside threads with OFD locks
fcntl34.c:33: TINFO: spawning '18' threads
tst_kernel.c:87: TINFO: uname.machine=aarch64 kernel is 64bit
fcntl34.c:63: TBROK: fcntl(4, F_OFD_SETLKW, { 1, 0, 0, 1, 0 }): EINVAL (22)

tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
fcntl34.c:87: TINFO: write to a file inside threads with OFD locks
fcntl34.c:33: TINFO: spawning '18' threads
tst_kernel.c:87: TINFO: uname.machine=aarch64 kernel is 64bit
fcntl34.c:63: TBROK: fcntl(4, F_OFD_SETLKW, { 1, 0, 0, 1, 0 }): EINVAL (22)

tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
fcntl36.c:288: TINFO: OFD read lock vs OFD write lock
tst_kernel.c:87: TINFO: uname.machine=aarch64 kernel is 64bit
fcntl36.c:166: TBROK: fcntl(3, F_OFD_SETLKW, { 0, 0, 0, 4096, 0 }): EINVAL (22)

tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
fcntl36.c:288: TINFO: OFD read lock vs OFD write lock
tst_kernel.c:87: TINFO: uname.machine=aarch64 kernel is 64bit
fcntl36.c:166: TBROK: fcntl(3, F_OFD_SETLKW, { 0, 0, 0, 4096, 0 }): EINVAL (22)

Test details links,
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230411/testrun/16168516/suite/ltp-syscalls/test/fcntl36/history/
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230411/testrun/16168516/suite/ltp-syscalls/test/fcntl34/history/
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230411/testrun/16168516/suite/ltp-syscalls/test/fcntl36/log

Steps to reproduce:

# To install tuxrun on your system globally:
# sudo pip3 install -U tuxrun==0.41.0
#
# See https://tuxrun.org/ for complete documentation.

tuxrun   \
 --runtime podman   \
 --device qemu-arm64   \
 --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2OGsEcyUv1ZWPkcY6bowUEt67EK/Image.gz
  \
 --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2OGsEcyUv1ZWPkcY6bowUEt67EK/modules.tar.xz
  \
 --rootfs https://storage.tuxsuite.com/public/linaro/lkft/oebuilds/2OFRZRfcnhLXEnzmi2qNYuD7o3k/images/am57xx-evm/lkft-tux-image-am57xx-evm-20230410193023.rootfs.ext4.gz
  \
 --parameters SKIPFILE=skipfile-lkft.yaml   \
 --parameters SHARD_NUMBER=10   \
 --parameters SHARD_INDEX=2   \
 --image docker.io/lavasoftware/lava-dispatcher:2023.01.0020.gc1598238f   \
 --tests ltp-syscalls   \
 --timeouts boot=30 ltp-syscalls=50


--
Linaro LKFT
https://lkft.linaro.org