linux-kernel - Re: [PATCH =-v3 18/21] fanotify: all userspace to set timeouts

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20081112165610.GD19669@infradead.org>
Date:	Wed, 12 Nov 2008 11:56:10 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Eric Paris <eparis@...hat.com>
Cc:	linux-kernel@...r.kernel.org, malware-list@...ts.printk.net,
	viro@...iv.linux.org.uk, alan@...rguk.ukuu.org.uk,
	arjan@...radead.org, greg@...ah.com, tytso@....edu,
	akpm@...ux-foundation.org
Subject: Re: [PATCH =-v3 18/21] fanotify: all userspace to set timeouts

On Wed, Nov 12, 2008 at 11:12:01AM -0500, Eric Paris wrote:
> fanotify when used to make access decisions has a default 5 second timeout.
> This patch will allow userspace listeners to change their timeout on a
> group wide basis.  Userspace listeners will still be able to reset the
> timeout for individual events.

Really, I think you start to over-engineer.  I think this whole stuff
would have a much higher chance if you could come up with a staged set
of patchsets, ala:

 (1) unify the current *notify schemes
 (2) add a filesystem wide notify scheme
 (3) add blocking filesystem notifiers

and then maybe a fourth with all the misc little things that I doubt
will have much of a chance.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/