diff options
author | hongnanli <hongnan.li@linux.alibaba.com> | 2022-02-11 11:19:28 +0800 |
---|---|---|
committer | Richard Weinberger <richard@nod.at> | 2022-03-16 22:02:48 +0100 |
commit | 163b438b510cf749cdd5e57fc5b40bf72fa09edb (patch) | |
tree | 225ad57a6000784191ba9b58472fffcafa9bb303 /fs/jffs2 | |
parent | c3c07fc25f37c157fde041b3a0c3dfcb1590cbce (diff) |
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 <hongnan.li@linux.alibaba.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'fs/jffs2')
-rw-r--r-- | fs/jffs2/jffs2_fs_i.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/jffs2/jffs2_fs_i.h b/fs/jffs2/jffs2_fs_i.h index 2e4a86763c07..93a2951538ce 100644 --- a/fs/jffs2/jffs2_fs_i.h +++ b/fs/jffs2/jffs2_fs_i.h @@ -18,11 +18,11 @@ #include <linux/mutex.h> 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; |