From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL io_uring fixes for 5.5-rc2
Date: Thu, 12 Dec 2019 18:20:51 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Here's a set of changes/fixes that should go into 5.5-rc. This pull
request contains:
- A tweak to IOSQE_IO_LINK (also marked for stable) to allow links that
don't sever if the result is < 0. This is mostly for linked timeouts,
where if we ask for a pure timeout we always get -ETIME. This makes
links useless for that case, hence allow a case where it works.
- Five minor optimizations to fix and improve cases that regressed
since v5.4.
- An SQTHREAD locking fix.
- A sendmsg/recvmsg iov assignment fix.
- Net fix where read_iter/write_iter don't honor IOCB_NOWAIT, and
subsequently ensuring that works for io_uring.
- Fix a case where for an invalid opcode we might return -EBADF instead
of -EINVAL, if the ->fd of that sqe was set to an invalid fd value.
Please pull!
git://git.kernel.dk/linux-block.git tags/io_uring-5.5-20191212
----------------------------------------------------------------
Jens Axboe (11):
io_uring: allow unbreakable links
io-wq: remove worker->wait waitqueue
io-wq: briefly spin for new work after finishing work
io_uring: sqthread should grab ctx->uring_lock for submissions
io_uring: deferred send/recvmsg should assign iov
io_uring: don't dynamically allocate poll data
io_uring: run next sqe inline if possible
io_uring: only hash regular files for async work execution
net: make socket read/write_iter() honor IOCB_NOWAIT
io_uring: add sockets to list of files that support non-blocking issue
io_uring: ensure we return -EINVAL on unknown opcode
fs/io-wq.c | 34 ++++++---
fs/io-wq.h | 7 +-
fs/io_uring.c | 168 +++++++++++++++++++++++-------------------
include/uapi/linux/io_uring.h | 40 +++++-----
net/socket.c | 4 +-
5 files changed, 146 insertions(+), 107 deletions(-)
--
Jens Axboe
reply other threads:[~2019-12-13 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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