fanotify: FMODE_NONOTIFY and __O_SYNC in sparc conflict

sparc used the same value as FMODE_NONOTIFY so change FMODE_NONOTIFY to be
something unique.

Signed-off-by: Wu Fengguang <[email protected]>
Signed-off-by: Eric Paris <[email protected]>
This commit is contained in:
Signed-off-by: Wu Fengguang authored and Eric Paris committed 2010-07-28 09:58:54 -04:00
1 parent ecf081d1a7
commit 12ed2e36c9
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -5,7 +5,7 @@
/*
* FMODE_EXEC is 0x20
* FMODE_NONOTIFY is 0x800000
* FMODE_NONOTIFY is 0x1000000
* These cannot be used by userspace O_* until internal and external open
* flags are split.
* -Eric Paris
+1 -1
View File
@@ -91,7 +91,7 @@ struct inodes_stat_t {
#define FMODE_RANDOM ((__force fmode_t)0x1000)
/* File was opened by fanotify and shouldn't generate fanotify events */
#define FMODE_NONOTIFY ((__force fmode_t)8388608)
#define FMODE_NONOTIFY ((__force fmode_t)16777216) /* 0x1000000 */
/*
* The below are the various read and write types that we support. Some of