From: hongnanli Date: Fri, 11 Feb 2022 03:19:28 +0000 (+0800) Subject: fs/jffs2: fix comments mentioning i_mutex X-Git-Tag: v6.1-rc5~1648^2~4 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=163b438b510cf749cdd5e57fc5b40bf72fa09edb;p=platform%2Fkernel%2Flinux-starfive.git fs/jffs2: fix comments mentioning i_mutex inode->i_mutex has been replaced with inode->i_rwsem long ago. Fix comments still mentioning i_mutex. Signed-off-by: hongnanli Signed-off-by: Richard Weinberger --- diff --git a/fs/jffs2/jffs2_fs_i.h b/fs/jffs2/jffs2_fs_i.h index 2e4a867..93a2951 100644 --- a/fs/jffs2/jffs2_fs_i.h +++ b/fs/jffs2/jffs2_fs_i.h @@ -18,11 +18,11 @@ #include struct jffs2_inode_info { - /* We need an internal mutex similar to inode->i_mutex. + /* We need an internal mutex similar to inode->i_rwsem. Unfortunately, we can't used the existing one, because either the GC would deadlock, or we'd have to release it before letting GC proceed. Or we'd have to put ugliness - into the GC code so it didn't attempt to obtain the i_mutex + into the GC code so it didn't attempt to obtain the i_rwsem for the inode(s) which are already locked */ struct mutex sem;