From: Carlos Llamas <cmllamas@google.com>
To: Joe Damato <jdamato@fastly.com>
Cc: Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
open list <linux-kernel@vger.kernel.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
William McVicker <willmcvicker@google.com>
Subject: Re: [PATCH vfs/vfs.fixes v2] eventpoll: Set epoll timeout if it's in the future
Date: Mon, 28 Apr 2025 22:32:31 +0000 [thread overview]
Message-ID: <aBAB_4gQ6O_haAjp@google.com> (raw)
In-Reply-To: <aA-xutxtw3jd00Bz@LQ3V64L9R2>
On Mon, Apr 28, 2025 at 09:50:02AM -0700, Joe Damato wrote:
> Thank you for spotting that and sorry for the trouble.
This was also flagged by our Android's epoll_pwait2 tests here:
https://android.googlesource.com/platform/bionic/+/refs/heads/main/tests/sys_epoll_test.cpp
They would all timeout, so the hang reported by Christian fits.
> Christian / Jan what would be the correct way for me to deal with
> this? Would it be to post a v3 (re-submitting the patch in its
> entirety) or to post a new patch that fixes the original and lists
> the commit sha from vfs.fixes with a Fixes tag ?
The original commit has landed in mainline already, so it needs to be
new patch at this point. If if helps, here is the tag:
Fixes: 0a65bc27bd64 ("eventpoll: Set epoll timeout if it's in the future")
> diff --git a/fs/eventpoll.c b/fs/eventpoll.c
> index 4bc264b854c4..1a5d1147f082 100644
> --- a/fs/eventpoll.c
> +++ b/fs/eventpoll.c
> @@ -2111,7 +2111,9 @@ static int ep_poll(struct eventpoll *ep, struct epoll_event __user *events,
>
> write_unlock_irq(&ep->lock);
>
> - if (!eavail && ep_schedule_timeout(to))
> + if (!ep_schedule_timeout(to))
> + timed_out = 1;
> + else if (!eavail)
> timed_out = !schedule_hrtimeout_range(to, slack,
> HRTIMER_MODE_ABS);
> __set_current_state(TASK_RUNNING);
I've ran your change through our internal CI and I confirm it fixes the
hangs seen on our end. If you send the fix feel free to add:
Tested-by: Carlos Llamas <cmllamas@google.com>
Cheers,
Carlos Llamas
next prev parent reply other threads:[~2025-04-28 22:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 18:58 [PATCH vfs/vfs.fixes v2] eventpoll: Set epoll timeout if it's in the future Joe Damato
2025-04-17 7:56 ` Christian Brauner
2025-04-26 12:29 ` Christian Brauner
2025-04-28 12:14 ` Jan Kara
2025-04-28 13:18 ` Tudor Ambarus
2025-04-28 13:32 ` Tudor Ambarus
2025-04-28 16:50 ` Joe Damato
2025-04-28 22:32 ` Carlos Llamas [this message]
2025-04-28 22:41 ` Joe Damato
2025-04-29 10:19 ` Jan Kara
2025-04-29 11:08 ` Christian Brauner
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=aBAB_4gQ6O_haAjp@google.com \
--to=cmllamas@google.com \
--cc=alexander.h.duyck@intel.com \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jack@suse.cz \
--cc=jdamato@fastly.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=tudor.ambarus@linaro.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willmcvicker@google.com \
/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