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
From:   Naresh Kamboju <naresh.kamboju@linaro.org>
Date:   Fri, 19 May 2023 14:47:21 +0530
Message-ID: <CA+G9fYs-Bc6wZKx+Fz4gFBQhkfRi+pQCnij5Kh3zhHU31mmGgQ@mail.gmail.com>
Subject: LTP: io_uring01 io_uring02 fails on compat mode - 64-bit kernel and
 32-bit userspace
To:     open list <linux-kernel@vger.kernel.org>,
        LTP List <ltp@lists.linux.it>, lkft-triage@lists.linaro.org
Cc:     Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
        Dan Carpenter <dan.carpenter@linaro.org>,
        chrubis <chrubis@suse.cz>, Petr Vorel <pvorel@suse.cz>,
        Anders Roxell <anders.roxell@linaro.org>,
        Martin Doucha <mdoucha@suse.cz>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

LTP running on compat mode where the tests run on
64-bit kernel and 32-bit userspace are noticed on a list of failures.

What would be the best way to handle this rare combination of failures ?

* qemu_x86_64-compat
   - io_uring01
   - io_uring02

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

tst_buffers.c:55: TINFO: Test is using guarded buffers
tst_test.c:1558: TINFO: Timeout per run is 0h 02m 30s
io_uring01.c:80: TPASS: io_uring_setup() passed
io_uring01.c:89: TBROK: mmap((nil),388,3,32769,3,0) failed: ENOMEM (12)

tst_test.c:1558: TINFO: Timeout per run is 0h 02m 30s
io_uring02.c:213: TBROK: mmap((nil),18752,3,32769,5,0) failed: ENOMEM (12)


log:
----

 - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-rc1-71-g105131df9c3b/testrun/16883235/suite/ltp-syscalls/test/io_uring02/log
 - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.4-rc1-71-g105131df9c3b/testrun/16883235/suite/ltp-syscalls/test/io_uring01/history/


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