All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Ben Noordhuis <info@bnoordhuis.nl>, io-uring@vger.kernel.org
Subject: Re: [PATCH] io_uring: undeprecate epoll_ctl support
Date: Tue, 2 May 2023 13:47:29 +0100	[thread overview]
Message-ID: <b6cca1a6-304c-ae72-c45f-7ee3b43cf00c@gmail.com> (raw)
In-Reply-To: <20230501185240.352642-1-info@bnoordhuis.nl>

On 5/1/23 19:52, Ben Noordhuis wrote:
> Libuv recently started using it so there is at least one consumer now.

It was rather deprecated because io_uring controlling epoll is a bad
idea and should never be used. One reason is that it means libuv still
uses epoll but not io_uring, and so the use of io_uring wouldn't seem
to make much sense. You're welcome to prove me wrong on that, why libuv
decided to use a deprecated API in the first place?
Sorry, but the warning is going to stay and libuv should revert the use
of epol_ctl requests.


> Link: https://github.com/libuv/libuv/pull/3979
> ---
>   io_uring/epoll.c | 4 ----
>   1 file changed, 4 deletions(-)
> 
> diff --git a/io_uring/epoll.c b/io_uring/epoll.c
> index 9aa74d2c80bc..89bff2068a19 100644
> --- a/io_uring/epoll.c
> +++ b/io_uring/epoll.c
> @@ -25,10 +25,6 @@ int io_epoll_ctl_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
>   {
>   	struct io_epoll *epoll = io_kiocb_to_cmd(req, struct io_epoll);
>   
> -	pr_warn_once("%s: epoll_ctl support in io_uring is deprecated and will "
> -		     "be removed in a future Linux kernel version.\n",
> -		     current->comm);
> -
>   	if (sqe->buf_index || sqe->splice_fd_in)
>   		return -EINVAL;
>   

-- 
Pavel Begunkov

  reply	other threads:[~2023-05-02 12:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 18:52 [PATCH] io_uring: undeprecate epoll_ctl support Ben Noordhuis
2023-05-02 12:47 ` Pavel Begunkov [this message]
2023-05-03  8:58   ` Ben Noordhuis
2023-05-03 12:49     ` Jens Axboe
2023-05-03 13:21       ` Pavel Begunkov
2023-05-03 13:42         ` Jens Axboe
2023-05-03 13:13     ` Pavel Begunkov
2023-05-03 14:55 ` Jens Axboe
2023-05-06  9:55   ` Ben Noordhuis
2023-05-27  1:48     ` Sam James
2023-05-27  2:22       ` Jens Axboe
2023-05-27  2: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 \
    --in-reply-to=b6cca1a6-304c-ae72-c45f-7ee3b43cf00c@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=info@bnoordhuis.nl \
    --cc=io-uring@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.