This is an automated email from the ASF dual-hosted git repository. acassis pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/nuttx.git
commit d5d134bc790bbee9e4473bbbb041bc8e754470eb Author: Xiang Xiao <[email protected]> AuthorDate: Mon Sep 14 21:04:23 2026 +0800 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 <[email protected]> --- fs/aio/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/aio/Kconfig b/fs/aio/Kconfig index 11d74133e43..d3feb4a58c2 100644 --- a/fs/aio/Kconfig +++ b/fs/aio/Kconfig @@ -13,7 +13,7 @@ config FS_AIO config FS_AIO_LISTIO_MAX int "Maximum number of AIO operations in listio" - default 10 + default 256 ---help--- This option sets the maximum number of asynchronous I/O (AIO) operations that can be submitted in a single call to lio_listio().
