* [PATCH] raid5: update comment in release_stripe_list
@ 2020-01-09 14:03 jgq516
0 siblings, 0 replies; only message in thread
From: jgq516 @ 2020-01-09 14:03 UTC (permalink / raw)
To: liu.song.a23; +Cc: linux-raid, Guoqing Jiang
From: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
After commit cf170f3fa451 ("raid5: avoid release list until last
reference of the stripe"), we only set STRIPE_ON_RELEASE_LIST bit
when sh->count is 1.
And no need to mention STRIPE_ON_UNPLUG_LIST here since the related
comment is already in raid5_unplug.
Signed-off-by: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
---
drivers/md/raid5.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 7f8504525435..6a8b5112afa9 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
@@ -368,8 +368,7 @@ static int release_stripe_list(struct r5conf *conf,
clear_bit(STRIPE_ON_RELEASE_LIST, &sh->state);
/*
* Don't worry the bit is set here, because if the bit is set
- * again, the count is always > 1. This is true for
- * STRIPE_ON_UNPLUG_LIST bit too.
+ * again, the count is always 1.
*/
hash = sh->hash_lock_index;
__release_stripe(conf, sh, &temp_inactive_list[hash]);
--
2.17.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2020-01-09 14:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-09 14:03 [PATCH] raid5: update comment in release_stripe_list jgq516
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.