io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 5.8-rc7
Date: Fri, 24 Jul 2020 10:49:14 -0600	[thread overview]
Message-ID: <c07ebe12-2b16-3811-9abc-d3e8d99b54db@kernel.dk> (raw)

Hi Linus,

- Fix discrepancy in how sqe->flags are treated for a few requests, this
  makes it consistent (Daniele)

- Ensure that poll driven retry works double waitqueue poll users

- Fix a missing io_req_init_async() (Pavel)

Please pull!


The following changes since commit 681fda8d27a66f7e65ff7f2d200d7635e64a8d05:

  io_uring: fix recvmsg memory leak with buffer selection (2020-07-15 13:35:56 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-5.8-2020-07-24

for you to fetch changes up to 3e863ea3bb1a2203ae648eb272db0ce6a1a2072c:

  io_uring: missed req_init_async() for IOSQE_ASYNC (2020-07-23 11:20:55 -0600)

----------------------------------------------------------------
io_uring-5.8-2020-07-24

----------------------------------------------------------------
Daniele Albano (1):
      io_uring: always allow drain/link/hardlink/async sqe flags

Jens Axboe (1):
      io_uring: ensure double poll additions work with both request types

Pavel Begunkov (1):
      io_uring: missed req_init_async() for IOSQE_ASYNC

 fs/io_uring.c | 61 +++++++++++++++++++++++++++++++++++------------------------
 1 file changed, 36 insertions(+), 25 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2020-07-24 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 16:49 Jens Axboe [this message]
2020-07-24 21:40 ` [GIT PULL] io_uring fixes for 5.8-rc7 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=c07ebe12-2b16-3811-9abc-d3e8d99b54db@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@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).