From: Dmitry Kadashev <dkadashev@gmail.com>
To: io-uring@vger.kernel.org
Cc: axboe@kernel.dk, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org,
Dmitry Kadashev <dkadashev@gmail.com>
Subject: [PATCH 0/2] io_uring: add mkdirat support
Date: Mon, 16 Nov 2020 11:45:27 +0700 [thread overview]
Message-ID: <20201116044529.1028783-1-dkadashev@gmail.com> (raw)
This adds mkdirat support to io_uring and is heavily based on recently
added renameat() / unlinkat() support.
The first patch is preparation with no functional changes, makes
do_mkdirat accept struct filename pointer rather than the user string.
The second one leverages that to implement mkdirat in io_uring.
Based on for-5.11/io_uring.
Dmitry Kadashev (2):
fs: make do_mkdirat() take struct filename
io_uring: add support for IORING_OP_MKDIRAT
fs/internal.h | 1 +
fs/io_uring.c | 58 +++++++++++++++++++++++++++++++++++
fs/namei.c | 20 ++++++++----
include/uapi/linux/io_uring.h | 1 +
4 files changed, 74 insertions(+), 6 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-16 4:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 4:45 Dmitry Kadashev [this message]
2020-11-16 4:45 ` [PATCH 1/2] fs: make do_mkdirat() take struct filename Dmitry Kadashev
2021-01-25 4:38 ` Jens Axboe
2021-01-26 22:55 ` Al Viro
2021-02-01 11:09 ` Dmitry Kadashev
2021-02-01 15:00 ` Al Viro
2021-02-01 15:29 ` Al Viro
2021-03-31 16:28 ` Eric W. Biederman
2021-03-31 16:46 ` Al Viro
2021-02-02 4:39 ` Dmitry Kadashev
2020-11-16 4:45 ` [PATCH 2/2] io_uring: add support for IORING_OP_MKDIRAT Dmitry Kadashev
2020-12-04 10:57 ` [PATCH 0/2] io_uring: add mkdirat support Dmitry Kadashev
2020-12-15 11:43 ` Dmitry Kadashev
2020-12-15 16:20 ` Jens Axboe
2020-12-16 6:05 ` Dmitry Kadashev
2021-01-20 8:21 ` Dmitry Kadashev
2021-01-26 22:35 ` Jens Axboe
2021-01-27 11:06 ` Dmitry Kadashev
2021-01-27 16:22 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2020-11-11 13:25 Dmitry Kadashev
2020-11-13 23:57 ` Jens Axboe
2020-11-16 4:42 ` Dmitry Kadashev
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=20201116044529.1028783-1-dkadashev@gmail.com \
--to=dkadashev@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).