From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring work-around for S_IFREG anon inodes
Date: Mon, 30 Jun 2025 15:17:54 -0600 [thread overview]
Message-ID: <c80c82d7-5727-4b8a-b995-2de1d5733103@kernel.dk> (raw)
Hi Linus,
Sending this one out early as the patch that broke io_uring is already in
6.15.4 stable, and I'd like to get the fix included for 6.15.5.
tldr is that now that anonymous inodes set S_IFREG, this breaks the
io_uring read/write retries for short reads/writes. As things like
timerfd and eventfd are anon inodes, applications that previously did:
unsigned long event_data[2];
io_uring_prep_read(sqe, evfd, event_data, sizeof(event_data), 0);
and just got a short read when 1 event was posted, will now wait for the
full amount before posting a completion. This caused issues for the
ghostty application, making it basically unusable due to excessive
buffering.
Please pull!
The following changes since commit 178b8ff66ff827c41b4fa105e9aabb99a0b5c537:
io_uring/kbuf: flag partial buffer mappings (2025-06-26 12:17:48 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.16-20250630
for you to fetch changes up to 6f11adcc6f36ffd8f33dbdf5f5ce073368975bc3:
io_uring: gate REQ_F_ISREG on !S_ANON_INODE as well (2025-06-29 16:52:34 -0600)
----------------------------------------------------------------
io_uring-6.16-20250630
----------------------------------------------------------------
Jens Axboe (1):
io_uring: gate REQ_F_ISREG on !S_ANON_INODE as well
io_uring/io_uring.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
Jens Axboe
next reply other threads:[~2025-06-30 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 21:17 Jens Axboe [this message]
2025-07-01 0:19 ` [GIT PULL] io_uring work-around for S_IFREG anon inodes pr-tracker-bot
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=c80c82d7-5727-4b8a-b995-2de1d5733103@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).