[RFC vfs/for-next 0/1] Only set epoll timeout if it's in the future

Joe Damato posted 1 patch 8 months, 1 week ago
fs/eventpoll.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
[RFC vfs/for-next 0/1] Only set epoll timeout if it's in the future
Posted by Joe Damato 8 months, 1 week ago
Greetings:

Sending as an RFC against vfs/for-next because I am not sure which
branch to send this against.

It's possible this should be against vfs.fixes with a Fixes
bf3b9f6372c4 ("epoll: Add busy poll support to epoll with socket
fds."), but I am not sure.

The commit message explains the issue in detail, please see the commit
message for details.

If this patch is appropriate, please let me know:
  - which branch to generate the patch against (I suspect vfs/for-next
    is wrong),
  - whether to include the fixes tag mentioned above or if this is
    considered "new code" instead of a bug fix and I'll omit the fixes.

I'll re-send as instructed (without this cover letter)... or not if this
patch is incorrect/not desirable :)

Thanks,
Joe

Joe Damato (1):
  eventpoll: Set epoll timeout if it's in the future

 fs/eventpoll.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)


base-commit: 2e72b1e0aac24a12f3bf3eec620efaca7ab7d4de
-- 
2.43.0
Re: [RFC vfs/for-next 0/1] Only set epoll timeout if it's in the future
Posted by Christian Brauner 8 months, 1 week ago
On Tue, Apr 15, 2025 at 06:43:45PM +0000, Joe Damato wrote:
> Greetings:
> 
> Sending as an RFC against vfs/for-next because I am not sure which
> branch to send this against.
> 
> It's possible this should be against vfs.fixes with a Fixes

Yes, can you resend against vfs.fixes, please? :)