From: Dmitry Kadashev <[email protected]>
To: Jens Axboe <[email protected]>, Alexander Viro <[email protected]>
Cc: Pavel Begunkov <[email protected]>,
[email protected], [email protected],
Dmitry Kadashev <[email protected]>
Subject: [PATCH v3 0/2] io_uring: add mkdirat support
Date: Tue, 30 Mar 2021 12:59:55 +0700 [thread overview]
Message-ID: <[email protected]> (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.13/io_uring.
Changes since v2:
- rebase
Changes since v1:
- do not mess with struct filename's refcount in do_mkdirat, instead add
and use __filename_create() that does not drop the name on success;
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 | 55 +++++++++++++++++++++++++++++++++++
fs/namei.c | 25 ++++++++++++----
include/uapi/linux/io_uring.h | 1 +
4 files changed, 76 insertions(+), 6 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-30 6:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 5:59 Dmitry Kadashev [this message]
2021-03-30 5:59 ` [PATCH v3 1/2] fs: make do_mkdirat() take struct filename Dmitry Kadashev
2021-03-30 7:17 ` Christian Brauner
2021-03-31 10:43 ` Dmitry Kadashev
2021-04-08 8:45 ` Dmitry Kadashev
2021-04-15 7:14 ` Dmitry Kadashev
2021-04-15 10:08 ` Christian Brauner
2021-04-15 10:09 ` Christian Brauner
2021-04-15 10:41 ` Dmitry Kadashev
2021-04-15 14:09 ` Christian Brauner
2021-05-13 7:45 ` Dmitry Kadashev
2021-05-14 15:11 ` Christian Brauner
2021-03-30 5:59 ` [PATCH v3 2/2] io_uring: add support for IORING_OP_MKDIRAT Dmitry Kadashev
2021-03-31 1:31 ` Al Viro
2021-03-31 10:38 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[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