IORING_OP_RECVMSG not respects non-blocking nature of the fd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: IORING_OP_RECVMSG not respects non-blocking nature of the fd
From: Norman Maurer <norman.maurer@xxxxxxxxxxxxxx>
Date: Tue, 16 Mar 2021 15:00:30 +0100

Hi there,

I think I found a bug in the current io_uring implementation. It seems like recvmsg currently not respect when a fd is set to non-blocking.  At the moment recvmsg never returns in this case. I can work around this by using MSG_DONTWAIT but I don’t think this should be needed.

I am using the latest 5.12 code base atm.

Bye
Norman

Follow-Ups:
- Re: IORING_OP_RECVMSG not respects non-blocking nature of the fd
  - From: Jens Axboe

Prev by Date: Re: [PATCH] Fix use-after-free in io_wqe_inc_running() due to wq already being free'd
Next by Date: [RFC PATCH v3 0/3] Async nvme passthrough over io_uring
Previous by thread: [PATCH] io_uring: remove duplicate IO_WQ_BIT_EXIT check
Next by thread: Re: IORING_OP_RECVMSG not respects non-blocking nature of the fd
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SoC] [Linux Rockchip SoC] [Linux Actions SoC] [Linux for Synopsys ARC Processors] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux