From: Hao Xu <hao.xu@linux.dev>
To: io-uring@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Pavel Begunkov <asml.silence@gmail.com>
Subject: [PATCH 0/5] misc update for openclose and provided buffer
Date: Fri, 10 Jun 2022 17:07:29 +0800 [thread overview]
Message-ID: <20220610090734.857067-1-hao.xu@linux.dev> (raw)
From: Hao Xu <howeyxu@tencent.com>
Patch 1 and 2 are bug fixes for openclose
Patch 3 is to support better close logic
Patch 4 is code clean
Patch 5 is a bug fix for ring-mapped provided buffer
Hao Xu (5):
io_uring: openclose: fix bug of closing wrong fixed file
io_uring: openclose: fix bug of unexpected return value in
IORING_CLOSE_FD_AND_FILE_SLOT mode
io_uring: openclose: support separate return value for
IORING_CLOSE_FD_AND_FILE_SLOT
io_uring: remove duplicate kbuf release
io_uring: kbuf: consume ring buffer in partial io case
io_uring/io_uring.c | 6 ------
io_uring/kbuf.c | 9 +++++++--
io_uring/kbuf.h | 10 ++++++++--
io_uring/openclose.c | 10 +++++++---
io_uring/rsrc.c | 2 +-
5 files changed, 23 insertions(+), 14 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-10 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 9:07 Hao Xu [this message]
2022-06-10 9:07 ` [PATCH 1/5] io_uring: openclose: fix bug of closing wrong fixed file Hao Xu
2022-06-10 9:07 ` [PATCH 2/5] io_uring: openclose: fix bug of unexpected return value in IORING_CLOSE_FD_AND_FILE_SLOT mode Hao Xu
2022-06-10 9:07 ` [PATCH 3/5] io_uring: openclose: support separate return value for IORING_CLOSE_FD_AND_FILE_SLOT Hao Xu
2022-06-10 9:07 ` [PATCH 4/5] io_uring: remove duplicate kbuf release Hao Xu
2022-06-10 9:07 ` [PATCH 5/5] io_uring: kbuf: fix bug of not consuming ring buffer in partial io case Hao Xu
2022-06-10 10:13 ` [PATCH 0/5] misc update for openclose and provided buffer Pavel Begunkov
2022-06-10 10:34 ` Hao Xu
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=20220610090734.857067-1-hao.xu@linux.dev \
--to=hao.xu@linux.dev \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox