diff options
| author | Eric Paris <eparis@redhat.com> | 2010-07-28 18:18:38 +0400 |
|---|---|---|
| committer | Eric Paris <eparis@redhat.com> | 2010-07-28 18:18:52 +0400 |
| commit | 700307a29ad61090dcf1d45f8f4a135f5e9211ae (patch) | |
| tree | 08b7969486c0039495684a6c13bbac3124a40348 /include/linux/fsnotify_backend.h | |
| parent | a4c6e9961fcb9da54648d98978d33c6fdcb7bb45 (diff) | |
| download | linux-700307a29ad61090dcf1d45f8f4a135f5e9211ae.tar.xz | |
fsnotify: use an explicit flag to indicate fsnotify_destroy_mark has been called
Currently fsnotify check is mark->group is NULL to decide if
fsnotify_destroy_mark() has already been called or not. With the upcoming
rcu work it is a heck of a lot easier to use an explicit flag than worry
about group being set to NULL.
Signed-off-by: Eric Paris <eparis@redhat.com>
Diffstat (limited to 'include/linux/fsnotify_backend.h')
| -rw-r--r-- | include/linux/fsnotify_backend.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/fsnotify_backend.h b/include/linux/fsnotify_backend.h index 3410d388163e..8e24cdf72928 100644 --- a/include/linux/fsnotify_backend.h +++ b/include/linux/fsnotify_backend.h @@ -300,6 +300,7 @@ struct fsnotify_mark { #define FSNOTIFY_MARK_FLAG_VFSMOUNT 0x02 #define FSNOTIFY_MARK_FLAG_OBJECT_PINNED 0x04 #define FSNOTIFY_MARK_FLAG_IGNORED_SURV_MODIFY 0x08 +#define FSNOTIFY_MARK_FLAG_ALIVE 0x10 unsigned int flags; /* vfsmount or inode mark? */ void (*free_mark)(struct fsnotify_mark *mark); /* called on final put+free */ }; |