From: Zhihao Cheng Date: Mon, 27 Dec 2021 03:22:34 +0000 (+0800) Subject: ubifs: Fix wrong number of inodes locked by ui_mutex in ubifs_inode comment X-Git-Tag: v6.6.17~7833^2~13 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=7a8884feec908afd05ebd45db5eba9a03674137e;p=platform%2Fkernel%2Flinux-rpi.git ubifs: Fix wrong number of inodes locked by ui_mutex in ubifs_inode comment Since 9ec64962afb1702f75b("ubifs: Implement RENAME_EXCHANGE") and 9e0a1fff8db56eaaebb("ubifs: Implement RENAME_WHITEOUT") are applied, ubifs_rename locks and changes 4 ubifs inodes, correct the comment for ui_mutex in ubifs_inode. Signed-off-by: Zhihao Cheng Signed-off-by: Richard Weinberger --- diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h index f55828c..008fa46 100644 --- a/fs/ubifs/ubifs.h +++ b/fs/ubifs/ubifs.h @@ -381,7 +381,7 @@ struct ubifs_gced_idx_leb { * @ui_mutex exists for two main reasons. At first it prevents inodes from * being written back while UBIFS changing them, being in the middle of an VFS * operation. This way UBIFS makes sure the inode fields are consistent. For - * example, in 'ubifs_rename()' we change 3 inodes simultaneously, and + * example, in 'ubifs_rename()' we change 4 inodes simultaneously, and * write-back must not write any of them before we have finished. * * The second reason is budgeting - UBIFS has to budget all operations. If an