From: Tvrtko Ursulin Subject: Re: fanotify - overall design before I start sending patches Date: Tue, 4 Aug 2009 17:09:50 +0100 Message-ID: <200908041709.51659.tvrtko.ursulin@sophos.com> References: <1248466429.3567.82.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "david-gFPdbfVZQbY@public.gmane.org" , "a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org" , "Valdis.Kletnieks-PjAqaU27lzQ@public.gmane.org" , Douglas Leeder , "malware-list-h+Im9A44IAFcMpApZELgcQ@public.gmane.org" , "mrkafk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" , "aviro-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , "jack-AlSwsSmVLrQ@public.gmane.org" , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "jengelh-nopoi9nDyk+ELgA04lAiVw@public.gmane.org" , "hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org" , "pavel-AlSwsSmVLrQ@public.gmane.org" , "alexl-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , "jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , "linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org" , "arjan-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org" To: Eric Paris Return-path: In-Reply-To: <1248466429.3567.82.camel@localhost> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: malware-list-bounces-h+Im9A44IAFcMpApZELgcQ@public.gmane.org Errors-To: malware-list-bounces-h+Im9A44IAFcMpApZELgcQ@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org Hi Eric, all, On Friday 24 July 2009 21:13:49 Eric Paris wrote: > If a FAN_ACCESS_PERM or FAN_OPEN_PERM event is received the listener > must send a response before the 5 second timeout. If no response is > sent before the 5 second timeout the original operation is allowed. If > this happens too many times (10 in a row) the fanotify group is evicted > from the kernel and will not get any new events. Sending a response is Would it make more sense to deny on timeouts and then evict? I am thinking it would be more secure with no significant drawbacks. Also for usages like HSM allowing it without data being in place might present wrong content to the user. > The only other current interface is the ability to ignore events by > superblock magic number. This makes it easy to ignore all events > in /proc which can be difficult to accomplish firing FANOTIFY_SET_MARK > with ignored_masks over and over as processes are created and destroyed. Just to double-check, that would also work for any other filesystem and is controllable from userspace? Tvrtko