From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Cc: code@mgjm.de
Subject: [PATCHSET 0/2] Incrementally consumed buffer fixes
Date: Thu, 19 Mar 2026 15:21:34 -0600 [thread overview]
Message-ID: <20260319212309.284152-1-axboe@kernel.dk> (raw)
Hi,
Michael reported two separate issues with incrementally consumed
buffers:
1) In case of EOF, or just a 0-byte read in general, BUF_MORE isn't
set. As further completions will happen from the given buffer,
it should be set.
2) For non-pollable files, the buffers are consumed upfront, yet
BUF_MORE is lost as the commit doesn't happen at completion time.
Fix both of these.
--
Jens Axboe
next reply other threads:[~2026-03-19 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 21:21 Jens Axboe [this message]
2026-03-19 21:21 ` [PATCH 1/2] io_uring/kbuf: fix missing BUF_MORE for incremental buffers at EOF Jens Axboe
2026-03-19 21:21 ` [PATCH 2/2] io_uring/kbuf: propagate BUF_MORE through early buffer commit path 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 \
--in-reply-to=20260319212309.284152-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=code@mgjm.de \
--cc=io-uring@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.