From: Christian Brauner <brauner@kernel.org>
To: Lin Feng <linf@wangsu.com>
Cc: Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
soheil@google.com, viro@zeniv.linux.org.uk, jack@suse.cz
Subject: Re: [PATCH] epoll: simplify ep_busy_loop by removing always 0 argument
Date: Thu, 27 Feb 2025 09:45:58 +0100 [thread overview]
Message-ID: <20250227-kanon-unrentabel-e3cf5eea0ded@brauner> (raw)
In-Reply-To: <20250227033412.5873-1-linf@wangsu.com>
On Thu, 27 Feb 2025 11:34:12 +0800, Lin Feng wrote:
> Commit 00b27634bc471("epoll: replace gotos with a proper loop") refactored
> ep_poll and always feeds ep_busy_loop with a time_out value of 0, nonblock
> mode for ep_busy_loop has sunk since, IOW nonblock mode checking has been
> taken over by ep_poll itself, codes snipped:
>
> static int ep_poll(struct eventpoll *ep...
> {
> ...
> if (timed_out)
> return 0;
>
> [...]
Applied to the vfs-6.15.misc branch of the vfs/vfs.git tree.
Patches in the vfs-6.15.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs-6.15.misc
[1/1] epoll: simplify ep_busy_loop by removing always 0 argument
https://git.kernel.org/vfs/vfs/c/d3a194d95fc8
prev parent reply other threads:[~2025-02-27 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 3:34 [PATCH] epoll: simplify ep_busy_loop by removing always 0 argument Lin Feng
2025-02-27 8:45 ` Christian Brauner [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 \
--in-reply-to=20250227-kanon-unrentabel-e3cf5eea0ded@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linf@wangsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soheil@google.com \
--cc=viro@zeniv.linux.org.uk \
/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.