blob: c1eff585f73eb6b1f462e6c3c2d627bb9b29174d [file] [log] [blame]
From 955eb72c1ae02433d70207c278df7f05d0bac5d7 Mon Sep 17 00:00:00 2001
From: Eric Sandeen <>
Date: Fri, 6 Dec 2019 10:55:59 -0600
Subject: [PATCH] fs: call fsnotify_sb_delete after evict_inodes
commit 1edc8eb2e93130e36ac74ac9c80913815a57d413 upstream.
When a filesystem is unmounted, we currently call fsnotify_sb_delete()
before evict_inodes(), which means that fsnotify_unmount_inodes()
must iterate over all inodes on the superblock looking for any inodes
with watches. This is inefficient and can lead to livelocks as it
iterates over many unwatched inodes.
At this point, SB_ACTIVE is gone and dropping refcount to zero kicks
the inode out out immediately, so anything processed by
fsnotify_sb_delete / fsnotify_unmount_inodes gets evicted in that loop.
After that, the call to evict_inodes will evict everything else with a
zero refcount.
This should speed things up overall, and avoid livelocks in
Signed-off-by: Eric Sandeen <>
Reviewed-by: Jan Kara <>
Signed-off-by: Al Viro <>
Signed-off-by: Paul Gortmaker <>
diff --git a/fs/notify/fsnotify.c b/fs/notify/fsnotify.c
index d53dc18a524e..ae9a4d1e4c71 100644
--- a/fs/notify/fsnotify.c
+++ b/fs/notify/fsnotify.c
@@ -57,6 +57,9 @@ static void fsnotify_unmount_inodes(struct super_block *sb)
* doing an __iget/iput with SB_ACTIVE clear would actually
* evict all inodes with zero i_count from icache which is
* unnecessarily violent and may in fact be illegal to do.
+ * However, we should have been called /after/ evict_inodes
+ * removed all zero refcount inodes, in any case. Test to
+ * be sure.
if (!atomic_read(&inode->i_count)) {
diff --git a/fs/super.c b/fs/super.c
index 2739f57515f8..691b202aa5c2 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -444,10 +444,12 @@ void generic_shutdown_super(struct super_block *sb)
sb->s_flags &= ~SB_ACTIVE;
- fsnotify_sb_delete(sb);
+ /* evict all inodes with zero refcount */
+ /* only nonzero refcount inodes can have marks */
+ fsnotify_sb_delete(sb);
if (sb->s_dio_done_wq) {