On Mon, Mar 26, 2012 at 01:03:43PM -0400, Eric Paris wrote: > How does this work with something like abrt, which causes core files to > be created in a known dir. It then watches (I have no idea if it uses > *notify) for new core files and processes them when they appear. Would > we be able to get any notification of core files with this patch? Maybe > we need a way to just not allow ourselves to block on core files? No we would not get notifications for core files with this patch any more. I see that this is a drawback for applications that want to track those files. But unfortunately I dont see how we could tell if a core file is created by a fanotify listener or not. The easiest thing would probably be if we had two flags, one to suppress "pure notification" events and one to suppress permission event. For example if we had: FMODE_NONOTIFY: suppress pure notification events FMODE_NOPERMNOTIFY: suppress permission events we would only use FMODE_NOPERMNOTIFY for core files then. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
