public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ming Lei <[email protected]>, [email protected]
Cc: Guang Wu <[email protected]>
Subject: Re: [v6.4 Regression] rust/io_uring: tests::net::test_tcp_recv_multi hangs
Date: Thu, 19 Oct 2023 05:31:11 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <ZTDjhCk8TC47oBdZ@fedora>

On 10/19/23 2:06 AM, Ming Lei wrote:
> Hello Jens,
> 
> Guang Wu found that tests::net::test_tcp_recv_multi in rust:io_uring
> hangs, and no such issue in RH test kernel.
> 
> - git clone https://github.com/tokio-rs/io-uring.git
> - cd io-uring
> - cargo run --package io-uring-test
> 
> I figured out that it is made by missing the last CQE with -ENOBUFS,
> which is caused by commit a2741c58ac67 ("io_uring/net: don't retry recvmsg()
> unnecessarily").
> 
> I am not sure if the last CQE should be returned and that depends how normal
> recv_multi is written, but IORING_CQE_F_MORE in the previous CQE shouldn't be
> returned at least.

Is this because it depends on this spurious retry? IOW, it adds N
buffers and triggers N receives, then depends on an internal extra retry
which would then yield -ENOBUFS? Because that sounds like a broken test.
As long as the recv triggers successfully, IORING_CQE_F_MORE will be
set. Only if it his some terminating condition would it trigger a CQE
without the MORE flag set. If it remains armed and ready to trigger
again, it will have MORE set. I'll take a look, this is pure guesswork
on my side right now.

We've done quite a lot of testing with recv multishot with this change,
and haven't had any issues. Which is why I'm a bit skeptical.

-- 
Jens Axboe


  reply	other threads:[~2023-10-19 11:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19  8:06 [v6.4 Regression] rust/io_uring: tests::net::test_tcp_recv_multi hangs Ming Lei
2023-10-19 11:31 ` Jens Axboe [this message]
2023-10-19 11:47   ` Ming Lei
2023-10-19 12:10     ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox