From: Jens Axboe <[email protected]>
To: Hillf Danton <[email protected]>, LKML <[email protected]>
Cc: [email protected], [email protected],
[email protected],
Pavel Begunkov <[email protected]>
Subject: Re: [PATCH] io_uring: fix file leak on creating io ctx
Date: Tue, 8 Dec 2020 08:50:56 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 12/8/20 3:28 AM, Hillf Danton wrote:
> On Mon, 7 Dec 2020 09:42:21 -0700 Jens Axboe wrote:
>> On 12/7/20 1:15 AM, Hillf Danton wrote:
>>> @@ -9207,12 +9208,14 @@ err_fd:
>>> #if defined(CONFIG_UNIX)
>>> ctx->ring_sock->file = file;
>>> #endif
>>> - if (unlikely(io_uring_add_task_file(ctx, file))) {
>>> - file = ERR_PTR(-ENOMEM);
>>> - goto err_fd;
>>> + ret = io_uring_add_task_file(ctx, file);
>>> + if (ret) {
>>> + fput(file);
>>> + put_unused_fd(fd);
>>> + goto err;
>>> }
>>> fd_install(ret, file);
>>> - return ret;
>>> + return 0;
>>
>> You're installing the return value from io_uring_add_task_file() in the
>> fd table, and then returning '0' for the fd...
>
> I canot find phrases to describe the stupid mistake in my patch.
> Thank you so much for pointing it out.
This one is still utterly broken, and (again) cannot have been even
tested in the most basic way. So let's focus on not how things are
phrased, but proper patch etiquette:
- Always (ALWAYS) test your patches. There's no excuse for not doing
so, and you are blacklisting yourself and ruining your reputation
by sending garbage that doesn't even pass basic functionality.
- If something isn't tested at all, make it VERY clear that this is
the case. Generally that's done by putting RFC in there and also
stating that this is just for discussion, it's not a patch that
is proposed for inclusion.
- Slow down! I see you sent a patch 10 min after this one, with no
extra notice in there why that was the case. It's clearly because
you figured out that this hasty send was bad.
I'd really like to get this in for 5.10, but I'd almost feel better
just redoing the patch myself to ensure it doesn't have other silly
errors in there. Don't put yourself in that position.
> @@ -9207,12 +9208,14 @@ err_fd:
> #if defined(CONFIG_UNIX)
> ctx->ring_sock->file = file;
> #endif
> - if (unlikely(io_uring_add_task_file(ctx, file))) {
> - file = ERR_PTR(-ENOMEM);
> - goto err_fd;
> + ret = io_uring_add_task_file(ctx, file);
> + if (ret) {
> + fput(file);
> + put_unused_fd(fd);
> + goto err;
> }
> - fd_install(ret, file);
> - return ret;
> + fd_install(fd, file);
> + return 0;
You're still returning '0' for the fd.
--
Jens Axboe
prev parent reply other threads:[~2020-12-08 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2020-12-07 15:04 ` [PATCH] io_uring: fix file leak on creating io ctx Jens Axboe
2020-12-07 15:42 ` Jens Axboe
2020-12-07 16:42 ` Jens Axboe
[not found] ` <[email protected]>
2020-12-08 15:50 ` Jens Axboe [this message]
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] \
[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