From: Linus Torvalds <[email protected]>
To: Jens Axboe <[email protected]>, Al Viro <[email protected]>,
Dmitry Kadashev <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: [GIT PULL] io_uring updates for 5.14-rc1
Date: Wed, 30 Jun 2021 13:05:44 -0700 [thread overview]
Message-ID: <CAHk-=wgCac9hBsYzKMpHk0EbLgQaXR=OUAjHaBtaY+G8A9KhFg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Tue, Jun 29, 2021 at 1:43 PM Jens Axboe <[email protected]> wrote:
>
> - Support for mkdirat, symlinkat, and linkat for io_uring (Dmitry)
I pulled this, and then I unpulled it again.
I hate how makes the rules for when "putname()" is called completely
arbitrary and very confusing. It ends up with multiple cases of
something like
error = -ENOENT;
goto out_putnames;
that didn't exist before.
And worse still ends up being that unbelievably ugly hack with
// On error `new` is freed by __filename_create, prevent extra freeing
// below
new = ERR_PTR(error);
goto out_putpath;
that ends up intentionally undoing one of the putnames because the
name has already been used.
And none of the commits have acks by Al. I realize that he can
sometimes be a bit unresponsive, but this is just *UGLY*. And we've
had too many io_uring issues for me to just say "I'm sure it's fine".
I can see a few ways to at least de-uglify things:
- Maybe we can make putname() just do nothing for IS_ERR_OR_NULL() names.
We have that kind of rules for a number of path walking things,
where passing in an error pointer is fine. Things like
link_path_walk() or filename_lookup() act that way very much by
design, exactly to make it easy to handle error conditions.
- callers of __filename_create() and similar thar eat the name (and
return a dentry or whatever) could then set the name to NULL, not as
part of the error handling, but unconditionally as a "it's been used".
So I think this is fixable.
But I'm *VERY* tired of io_uring being so buggy and doing "exciting"
things, and when it then starts affecting very core functionality and
I don't even see ack's from the one person who understands all of
that, I put my foot down.
No more flaky io_uring pulls. Give me the unambiguously good stuff,
not this kind of unacked ugly stuff.
Linus
next prev parent reply other threads:[~2021-06-30 20:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 20:43 [GIT PULL] io_uring updates for 5.14-rc1 Jens Axboe
2021-06-30 20:05 ` Linus Torvalds [this message]
2021-06-30 20:14 ` Jens Axboe
2021-06-30 20:18 ` Linus Torvalds
2021-06-30 20:21 ` Jens Axboe
2021-07-02 11:32 ` Dmitry Kadashev
2021-07-02 18:33 ` Linus Torvalds
2021-07-03 15:26 ` Dmitry Kadashev
2021-07-05 21:40 ` Linus Torvalds
2021-07-06 12:06 ` Dmitry Kadashev
-- strict thread matches above, loose matches on Subject: below --
2021-07-01 15:24 Jens Axboe
2021-07-01 19:20 ` pr-tracker-bot
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='CAHk-=wgCac9hBsYzKMpHk0EbLgQaXR=OUAjHaBtaY+G8A9KhFg@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