mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Damato <jdamato@fastly.com>
To: linux-fsdevel@vger.kernel.org
Cc: Joe Damato <jdamato@fastly.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	linux-kernel@vger.kernel.org (open list)
Subject: [RFC vfs/for-next 0/1] Only set epoll timeout if it's in the future
Date: Tue, 15 Apr 2025 18:43:45 +0000	[thread overview]
Message-ID: <20250415184346.39229-1-jdamato@fastly.com> (raw)

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


             reply	other threads:[~2025-04-15 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 18:43 Joe Damato [this message]
2025-04-15 18:43 ` [RFC vfs/for-next 1/1] eventpoll: Set " Joe Damato
2025-04-16  9:12   ` Jan Kara
2025-04-16 14:23 ` [RFC vfs/for-next 0/1] Only set " 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=20250415184346.39229-1-jdamato@fastly.com \
    --to=jdamato@fastly.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®