[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CA+G9fYs-Bc6wZKx+Fz4gFBQhkfRi+pQCnij5Kh3zhHU31mmGgQ@mail.gmail.com>
Date: Fri, 19 May 2023 14:47:21 +0530
From: Naresh Kamboju <naresh.kamboju@...aro.org>
To: open list <linux-kernel@...r.kernel.org>,
LTP List <ltp@...ts.linux.it>, lkft-triage@...ts.linaro.org
Cc: Arnd Bergmann <arnd@...db.de>, Ard Biesheuvel <ardb@...nel.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
chrubis <chrubis@...e.cz>, Petr Vorel <pvorel@...e.cz>,
Anders Roxell <anders.roxell@...aro.org>,
Martin Doucha <mdoucha@...e.cz>
Subject: LTP: io_uring01 io_uring02 fails on compat mode - 64-bit kernel and
32-bit userspace
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@...aro.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
Powered by blists - more mailing lists