From: Dmitry Kadashev <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH 0/2] io_uring: add mkdirat support
Date: Tue, 15 Dec 2020 18:43:26 +0700 [thread overview]
Message-ID: <CAOKbgA7MdAF1+MQePoZHALxNC5ye207ET=4JCqvdNcrGTcrkpw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Fri, Dec 4, 2020 at 5:57 PM Dmitry Kadashev <[email protected]> wrote:
>
> On Mon, Nov 16, 2020 at 11:45:27AM +0700, Dmitry Kadashev wrote:
> > 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
> >
>
> Hi Al Viro,
>
> Ping. Jens mentioned before that this looks fine by him, but you or
> someone from fsdevel should approve the namei.c part first.
Another ping.
Jens, you've mentioned the patch looks good to you, and with quite similar
changes (unlinkat, renameat) being sent for 5.11 is there anything that I can do
to help this to be accepted (not necessarily for 5.11 at this point)?
next prev parent reply other threads:[~2020-12-15 11:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 4:45 [PATCH 0/2] io_uring: add mkdirat support Dmitry Kadashev
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 [this message]
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='CAOKbgA7MdAF1+MQePoZHALxNC5ye207ET=4JCqvdNcrGTcrkpw@mail.gmail.com' \
[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