Skip to content

direct-io: remove IOCB_NOWAIT support#1415

Open
vfsci-bot[bot] wants to merge 2 commits into
vfs.base.cifrom
pw/1096344/vfs.base.ci
Open

direct-io: remove IOCB_NOWAIT support#1415
vfsci-bot[bot] wants to merge 2 commits into
vfs.base.cifrom
pw/1096344/vfs.base.ci

Conversation

@vfsci-bot
Copy link
Copy Markdown

@vfsci-bot vfsci-bot Bot commented May 18, 2026

Series: https://patchwork.kernel.org/project/linux-fsdevel/list/?series=1096344
Submitter: Christoph Hellwig
Version: 1
Patches: 2/2
Message-ID: <20260518063336.507369-2-hch@lst.de>
Base: vfs.base.ci
Lore: https://lore.kernel.org/linux-fsdevel/20260518063336.507369-2-hch@lst.de


Automated by ml2pr

Christoph Hellwig added 2 commits May 18, 2026 08:02
None of the file systems using the legacy direct I/O code actually sets
FMODE_NOWAIT, and if they did this would not work, as the write locking
could not handle the retry.  Remove this dead code.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Commit abb3046 ("block: mark bio_wouldblock_error() bio with
BIO_QUIET") added this to suppress buffer_head warnings, but neither
when this commit was added nor now any buffer_head using code actually
ever sets REQ_NOWAIT which can lead to BLK_STS_AGAIN.

Remove the special handling for now.  If we ever plan to use REQ_NOWAIT
for buffer_head based I/O we're better off handling BLK_STS_AGAIN in
the completion handler as it actually needs to retry the I/O as well.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants