aboutsummaryrefslogtreecommitdiffstats
path: root/fs/notify/vfsmount_mark.c
diff options
context:
space:
mode:
authorEric Paris <eparis@redhat.com>2010-07-28 10:18:38 -0400
committerEric Paris <eparis@redhat.com>2010-07-28 10:18:52 -0400
commit700307a29ad61090dcf1d45f8f4a135f5e9211ae (patch)
tree08b7969486c0039495684a6c13bbac3124a40348 /fs/notify/vfsmount_mark.c
parenta4c6e9961fcb9da54648d98978d33c6fdcb7bb45 (diff)
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 'fs/notify/vfsmount_mark.c')
-rw-r--r--fs/notify/vfsmount_mark.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/notify/vfsmount_mark.c b/fs/notify/vfsmount_mark.c
index b7ae64030021..56772b578fbd 100644
--- a/fs/notify/vfsmount_mark.c
+++ b/fs/notify/vfsmount_mark.c
@@ -145,7 +145,7 @@ int fsnotify_add_vfsmount_mark(struct fsnotify_mark *mark,
145 struct hlist_node *node, *last = NULL; 145 struct hlist_node *node, *last = NULL;
146 int ret = 0; 146 int ret = 0;
147 147
148 mark->flags = FSNOTIFY_MARK_FLAG_VFSMOUNT; 148 mark->flags |= FSNOTIFY_MARK_FLAG_VFSMOUNT;
149 149
150 assert_spin_locked(&mark->lock); 150 assert_spin_locked(&mark->lock);
151 assert_spin_locked(&group->mark_lock); 151 assert_spin_locked(&group->mark_lock);