[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <2709ed98-6459-70ea-50d4-f24b7278fb24@gnuweeb.org>
Date: Thu, 21 Jul 2022 06:21:24 +0700
From: Ammar Faizi <ammarfaizi2@...weeb.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: Pavel Begunkov <asml.silence@...il.com>,
Fernanda Ma'rouf <fernandafmr12@...weeb.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
io-uring Mailing List <io-uring@...r.kernel.org>,
GNU/Weeb Mailing List <gwml@...r.gnuweeb.org>
Subject: Linux 5.19-rc7 liburing test `poll-mshot-overflow.t` and
`read-write.t` fail
Hello Jens,
Kernel version:
commit ff6992735ade75aae3e35d16b17da1008d753d28
Author: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Sun Jul 17 13:30:22 2022 -0700
Linux 5.19-rc7
liburing version:
commit 4e6eec8bdea906fe5341c97aef96986d605004e9 (HEAD, origin/master, origin/HEAD)
Author: Dylan Yudaken <dylany@...com>
Date: Mon Jul 18 06:34:29 2022 -0700
fix io_uring_recvmsg_cmsg_nexthdr logic
io_uring_recvmsg_cmsg_nexthdr was using the payload to delineate the end
of the cmsg list, but really it needs to use whatever was returned by the
kernel.
Reported-and-tested-by: Jens Axboe <axboe@...nel.dk>
Fixes: 874406f7fb09 ("add multishot recvmsg API")
Signed-off-by: Dylan Yudaken <dylany@...com>
Link: https://lore.kernel.org/r/20220718133429.726628-1-dylany@fb.com
Signed-off-by: Jens Axboe <axboe@...nel.dk>
Two liburing tests fail:
Tests failed: <poll-mshot-overflow.t> <read-write.t>
make[1]: *** [Makefile:237: runtests] Error 1
make[1]: Leaving directory '/home/ammarfaizi2/app/liburing/test'
make: *** [Makefile:21: runtests] Error 2
ammarfaizi2@...egral2:~/app/liburing$ uname -a
Linux integral2 5.19.0-rc7-2022-07-18 #1 SMP PREEMPT_DYNAMIC Mon Jul 18 15:42:27 WIB 2022 x86_64 x86_64 x86_64 GNU/Linux
ammarfaizi2@...egral2:~/app/liburing$ test/read-write.t
cqe res -22, wanted 8192
test_buf_select vec failed
ammarfaizi2@...egral2:~/app/liburing$ test/poll-mshot-overflow.t
signalled no more!
ammarfaizi2@...egral2:~/app/liburing$
JFYI, -22 is -EINVAL.
read-write.t call trace when calling fprintf(..., "cqe res %d, wanted %d\n", ...):
#0 ___fprintf_chk (./debug/fprintf_chk.c:25)
#1 fprintf (/usr/include/x86_64-linux-gnu/bits/stdio2.h:105)
#2 __test_io (read-write.c:181)
#3 test_buf_select (read-write.c:577)
#4 main (read-write.c:849)
poll-mshot-overflow.t call trace should be trivial.
--
Ammar Faizi
Powered by blists - more mailing lists