Xiang Xiao d5d134bc79 fs/aio: raise the default AIO_LISTIO_MAX so LTP keeps passing ... The new CONFIG_FS_AIO_LISTIO_MAX option defaults to 10 and lio_listio() now rejects nent > {AIO_LISTIO_MAX} with EINVAL. The LTP release pinned by apps/testing/ltp (20230516) submits 256 requests in a single batch from conformance/interfaces/lio_listio/2-1.c, so ltp_interfaces_lio_listio_2_1 now fails on every configuration that enables CONFIG_TESTING_LTP (sim:citest, rv-virt:citest, sim:posix_test): lio_listio/2-1.c Error at lio_listio() 22: Invalid argument The EINVAL check itself is required by POSIX, so keep it and raise the default instead; the limit no longer costs memory because the requests are linked through the aiocb's own lio_link. While here, keep _POSIX_AIO_LISTIO_MAX at its POSIX-mandated value of 2 and let AIO_LISTIO_MAX carry the configurable implementation limit. Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>		2026-09-14 17:12:49 -03:00
..
aio.h
aio_cancel.c
aio_fsync.c
aio_initialize.c
aio_queue.c
aio_read.c
aio_signal.c
aio_write.c
aioc_contain.c
CMakeLists.txt
Kconfig
lio_listio.c
Make.defs