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
| ||
|
Date: Fri, 28 Aug 2009 14:55:42 -0400 From: Eric Paris <eparis@...hat.com> To: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, netdev@...r.kernel.org Cc: davem@...emloft.net, viro@...iv.linux.org.uk, alan@...ux.intel.com, hch@...radead.org Subject: [PATCH 1/9] task_struct: add PF_NONOTIFY for fanotify to use Since fanotify opens file descriptors inside the kernel for it's listeners it needs a way to make sure that 2 fanotify listeners, both which listen to open events do not continuously see each others open events (and get into a livelock reporting on each other's activity). This fix is to create a new tast_struct flags called PF_NONOTIFY. If this flag is set in a task no fanotify events will be generated for that task. fanotify will set the flag before and open call and will clear it immediately after. Signed-off-by: Eric Paris <eparis@...hat.com> --- include/linux/sched.h | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/include/linux/sched.h b/include/linux/sched.h index b88872f..3c1ce66 100644 --- a/include/linux/sched.h +++ b/include/linux/sched.h @@ -1695,6 +1695,7 @@ extern cputime_t task_gtime(struct task_struct *p); #define PF_EXITING 0x00000004 /* getting shut down */ #define PF_EXITPIDONE 0x00000008 /* pi exit done on shut down */ #define PF_VCPU 0x00000010 /* I'm a virtual CPU */ +#define PF_NONOTIFY 0x00000020 /* In fanotify open operation */ #define PF_FORKNOEXEC 0x00000040 /* forked but didn't exec */ #define PF_MCE_PROCESS 0x00000080 /* process policy on mce errors */ #define PF_SUPERPRIV 0x00000100 /* used super-user privileges */ -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists