Commit 12ba6676 authored by XU pengfei's avatar XU pengfei Committed by Song Liu

md/raid5: Fix spelling mistakes in comments

Fix spelling of 'waitting' in comments.
Signed-off-by: default avatarXU pengfei <xupengfei@nfschina.com>
Signed-off-by: default avatarSong Liu <song@kernel.org>
parent 9713a670
...@@ -1327,9 +1327,9 @@ static void r5l_write_super_and_discard_space(struct r5l_log *log, ...@@ -1327,9 +1327,9 @@ static void r5l_write_super_and_discard_space(struct r5l_log *log,
* superblock is updated to new log tail. Updating superblock (either * superblock is updated to new log tail. Updating superblock (either
* directly call md_update_sb() or depend on md thread) must hold * directly call md_update_sb() or depend on md thread) must hold
* reconfig mutex. On the other hand, raid5_quiesce is called with * reconfig mutex. On the other hand, raid5_quiesce is called with
* reconfig_mutex hold. The first step of raid5_quiesce() is waitting * reconfig_mutex hold. The first step of raid5_quiesce() is waiting
* for all IO finish, hence waitting for reclaim thread, while reclaim * for all IO finish, hence waiting for reclaim thread, while reclaim
* thread is calling this function and waitting for reconfig mutex. So * thread is calling this function and waiting for reconfig mutex. So
* there is a deadlock. We workaround this issue with a trylock. * there is a deadlock. We workaround this issue with a trylock.
* FIXME: we could miss discard if we can't take reconfig mutex * FIXME: we could miss discard if we can't take reconfig mutex
*/ */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment