ubifs: Fix wrong number of inodes locked by ui_mutex in ubifs_inode comment

Zhihao Cheng · richardweinberger · commit 7a8884feec90 · 2022-01-09T21:35:38.000+01:00
Since 9ec6496("ubifs: Implement RENAME_EXCHANGE") and 9e0a1ff("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 <chengzhihao1@huawei.com> Signed-off-by: Richard Weinberger <richard@nod.at>
diff --git 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

Original file line number	Diff line number	Diff line change
`@@ -381,7 +381,7 @@ struct ubifs_gced_idx_leb {`
`381`	`381`	`* @ui_mutex exists for two main reasons. At first it prevents inodes from`
`382`	`382`	`* being written back while UBIFS changing them, being in the middle of an VFS`
`383`	`383`	`* operation. This way UBIFS makes sure the inode fields are consistent. For`
`384`		`- * example, in 'ubifs_rename()' we change 3 inodes simultaneously, and`
	`384`	`+ * example, in 'ubifs_rename()' we change 4 inodes simultaneously, and`
`385`	`385`	`* write-back must not write any of them before we have finished.`
`386`	`386`	`*`
`387`	`387`	`* The second reason is budgeting - UBIFS has to budget all operations. If an`