From: Dmitry Kadashev <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 0/2] io_uring: add mkdirat support
Date: Mon, 16 Nov 2020 11:42:47 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, Nov 13, 2020 at 04:57:13PM -0700, Jens Axboe wrote:
> On 11/11/20 6:25 AM, 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.
>
> Looks good to me - you should send the first patch to linux-fsdevel (and
> CC Al Viro), really needs to be acked on that side before it can go in.
I'll resend the whole series with Al Viro and linux-fsdevel CCed, hope
that is OK, gives them a bit more context and they can ignore the
io_uring part. Hope that is OK.
> Also, have you written some test cases?
Yes, as part of liburing change - I'll send that shortly.
--
Dmitry Kadashev
next prev parent reply other threads:[~2020-11-16 4:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 13:25 [PATCH 0/2] io_uring: add mkdirat support Dmitry Kadashev
2020-11-11 13:25 ` [PATCH 1/2] fs: make do_mkdirat() take struct filename Dmitry Kadashev
2020-11-11 13:25 ` [PATCH 2/2] io_uring: add support for IORING_OP_MKDIRAT Dmitry Kadashev
2020-11-13 23:57 ` [PATCH 0/2] io_uring: add mkdirat support Jens Axboe
2020-11-16 4:42 ` Dmitry Kadashev [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-16 4:45 Dmitry Kadashev
2020-12-04 10:57 ` 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
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] \
/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