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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250416-drakonische-sanduhr-56d6363d1c12@brauner>
Date: Wed, 16 Apr 2025 16:23:24 +0200
From: Christian Brauner <brauner@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: linux-fsdevel@...r.kernel.org, 
	Alexander Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>, 
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [RFC vfs/for-next 0/1] Only set epoll timeout if it's in the
 future

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? :)