Messages in this thread Patch in this message | | | From | Geliang Tang <> | Subject | [PATCH] fsnotify: use list_next_entry in fsnotify_unmount_inodes | Date | Mon, 16 Nov 2015 22:18:38 +0800 |
| |
To make the intention clearer, use list_next_entry instead of list_entry.
Signed-off-by: Geliang Tang <geliangtang@163.com> --- fs/notify/inode_mark.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/notify/inode_mark.c b/fs/notify/inode_mark.c index e785fd9..741077d 100644 --- a/fs/notify/inode_mark.c +++ b/fs/notify/inode_mark.c @@ -199,8 +199,7 @@ void fsnotify_unmount_inodes(struct super_block *sb) break; } spin_unlock(&next_i->i_lock); - next_i = list_entry(next_i->i_sb_list.next, - struct inode, i_sb_list); + next_i = list_next_entry(next_i, i_sb_list); } /* -- 2.5.0
| |