[PATCHSET,0/3] Improve FMODE_NOWAIT coverage

Message ID	20230509151910.183637-1-axboe@kernel.dk (mailing list archive)
Headers	show Return-Path: <io-uring-owner@vger.kernel.org> From: Jens Axboe <axboe@kernel.dk> To: io-uring@vger.kernel.org Cc: torvalds@linux-foundation.org Subject: [PATCHSET 0/3] Improve FMODE_NOWAIT coverage Date: Tue, 9 May 2023 09:19:07 -0600 Message-Id: <20230509151910.183637-1-axboe@kernel.dk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	Improve FMODE_NOWAIT coverage \| expand [PATCHSET,0/3] Improve FMODE_NOWAIT coverage [1/3] net: set FMODE_NOWAIT for sockets [2/3] block: mark bdev files as FMODE_NOWAIT if underlying device supports it [3/3] io_uring: rely solely on FMODE_NOWAIT

Message ID

20230509151910.183637-1-axboe@kernel.dk (mailing list archive)

Headers

From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: torvalds@linux-foundation.org
Subject: [PATCHSET 0/3] Improve FMODE_NOWAIT coverage
Date: Tue,  9 May 2023 09:19:07 -0600
Message-Id: <20230509151910.183637-1-axboe@kernel.dk>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

Improve FMODE_NOWAIT coverage | expand

Message

Jens Axboe May 9, 2023, 3:19 p.m. UTC

Hi,

io_uring jumps through some hoops to check block devices and sockets
for sanity wrt nonblocking read/write attempts. We can get rid of that
if we just flag sockets and block devices as being sane in that regard.
Patches 1-2 do that for sockets and block devices, and then patch 3 can
remove some cruft on the io_uring side that is pretty ugly.