On Tuesday 26 Oct 2010 14:58:34 Vasily Novikov wrote: > > > 2. As I understood it was intended to flush cache via FAN_MARK_FLUSH > > > flag but it is currently disabled and there is no notion about it in > > > the man page. There are cases when it is necessary to flush all cache, > > > for example on anti-malware bases update. > > > > Where do you see this as disabled? > > In fanotify_mark syscall flags argument is checked and if FAN_MARK_FLUSH > bit is set then EINVAL error is returned. [snip] > 40 #define FAN_ALL_MARK_FLAGS (FAN_MARK_ADD |\ > 41 FAN_MARK_REMOVE |\ > 42 FAN_MARK_DONT_FOLLOW |\ > 43 FAN_MARK_ONLYDIR |\ > 44 FAN_MARK_MOUNT |\ > 45 FAN_MARK_IGNORED_MASK |\ > 46 FAN_MARK_IGNORED_SURV_MODIFY) > > fs/notify/fanotify/fanotify_user.c: > 678 SYSCALL_DEFINE(fanotify_mark)(int fanotify_fd, unsigned int > flags, > 679 __u64 mask, int dfd, > 680 const char __user * pathname) > ... > 696 if (flags & ~FAN_ALL_MARK_FLAGS) > 697 return -EINVAL; You are right. I suspect it is just an accidental omission of FAN_MARK_FLUSH from FAN_ALL_MARK_FLAGS. Eric would probably appreciate if you send him a patch for this since he is quite busy these days. Tvrtko Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom. Company Reg No 2096520. VAT Reg No GB 348 3873 20. -- 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
