[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171108004354.40308-1-shakeelb@google.com>
Date: Tue, 7 Nov 2017 16:43:54 -0800
From: Shakeel Butt <shakeelb@...gle.com>
To: Alexander Viro <viro@...iv.linux.org.uk>,
Greg Thelen <gthelen@...gle.com>, Jan Kara <jack@...e.cz>,
Michal Hocko <mhocko@...e.com>,
Johannes Weiner <hannes@...xchg.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Shakeel Butt <shakeelb@...gle.com>
Subject: [PATCH] vfs: remove might_sleep() from clear_inode()
Commit 7994e6f72543 ("vfs: Move waiting for inode writeback from
end_writeback() to evict_inode()") removed inode_sync_wait() from
end_writeback() and commit dbd5768f87ff ("vfs: Rename end_writeback()
to clear_inode()") renamed end_writeback() to clear_inode(). After
these patches there is no sleeping operation in clear_inode(). So,
remove might_sleep() from it.
Signed-off-by: Shakeel Butt <shakeelb@...gle.com>
---
fs/inode.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/inode.c b/fs/inode.c
index d1e35b53bb23..528f3159b928 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -497,7 +497,6 @@ EXPORT_SYMBOL(__remove_inode_hash);
void clear_inode(struct inode *inode)
{
- might_sleep();
/*
* We have to cycle tree_lock here because reclaim can be still in the
* process of removing the last page (in __delete_from_page_cache())
--
2.15.0.403.gc27cc4dac6-goog
Powered by blists - more mailing lists