Bug fix for recent batching change
cover Bug fix for recent batching change
Hey,
We hit another bug on my recent batching patch. In this case the bug has never been hit with the current md/md-next branch but some other patches we were working on changed the timing such that we hit this bug. It is theoretically possible to hit in the md/md-next batch so this patchset contains a fix.
The fix is the last commit. The first four commits are some basic refactoring that makes the final commit a bit easier.
A git repo is here and is based on current md/md-next (7a6f9e9cf1):
https://github.com/sbates130272/linux-p2pmem raid5_batch_quiesce
Thanks,
Logan
--
Logan Gunthorpe (5):
md/raid5: Refactor raid5_get_active_stripe()
md/raid5: Make is_inactive_blocked() helper
md/raid5: Drop unnecessary call to r5c_check_stripe_cache_usage() md/raid5: Move stripe_request_ctx up
md/raid5: Ensure batch_last is released before sleeping for quiesce
drivers/md/raid5.c | 162 ++++++++++++++++++++++++++++----------------- drivers/md/raid5.h | 2 +- 2 files changed, 101 insertions(+), 63 deletions(-)
base-commit: 7a6f9e9cf1befa0a1578501966d3c9b0cae46727 --
2.30.2
PATCH 1/5 md/raid5: Refactor raid5_get_active_stripe()
Refactor the raid5_get_active_stripe() to read more linearly in the order it's typically executed.
The init_stripe() call is called if a free stripe is found and the function is exited early which removes a lot of if (sh) checks and unindents the following code.
Remove the while loop in favour of the 'goto retry' pattern, which reduces indentation further. And use a 'goto wait_for_stripe' instead of an additional indent seeing it is the unusual path and this makes the code easier to read.
No functional changes intended. Will make subsequent changes in patches easier to understand.
--- drivers/md/raid5.c | 67 +++++++++++++++++++++++++--------------------- 1 file changed, 36 insertions(+), 31 deletions(-)
drivers/md/raid5.c +36 -31
@@ -766,41 +766,46 @@ raid5_get_active_stripe(struct r5conf *conf, sector_t sector,spin_lock_irq (conf->hash_locks + hash); -do { -wait_event_lock_irq (conf->wait_for_quiescent, - conf->quiesce ==0 || noquiesce, - *(conf->hash_locks + hash)); - sh =find_get_stripe (conf, sector, conf->generation - previous, - hash); -if (sh) -break ; +retry: +wait_event_lock_irq (conf->wait_for_quiescent, + conf->quiesce ==0 || noquiesce, + *(conf->hash_locks + hash)); + sh =find_get_stripe (conf, sector, conf->generation - previous, hash); +if (sh) + goto out; -if (!test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) { - sh =get_free_stripe (conf, hash); -if (!sh && !test_bit (R5_DID_ALLOC , &conf->cache_state)) -set_bit (R5_ALLOC_MORE , &conf->cache_state); - } -if (noblock && !sh) -break ; +if (test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) + goto wait_for_stripe; + sh =get_free_stripe (conf, hash); +if (sh) {r5c_check_stripe_cache_usage (conf); -if (!sh) { -set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); -r5l_wake_reclaim (conf->log,0 ); -wait_event_lock_irq (conf->wait_for_stripe, - !list_empty (conf->inactive_list + hash) && - (atomic_read (&conf->active_stripes) - < (conf->max_nr_stripes *3 /4 ) - || !test_bit (R5_INACTIVE_BLOCKED , - &conf->cache_state)), - *(conf->hash_locks + hash)); -clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); - }else { -init_stripe (sh, sector, previous); -atomic_inc (&sh->count); - } - }while (sh ==NULL ); +init_stripe (sh, sector, previous); +atomic_inc (&sh->count); + goto out; + } +if (!test_bit (R5_DID_ALLOC , &conf->cache_state)) +set_bit (R5_ALLOC_MORE , &conf->cache_state); + +wait_for_stripe: +if (noblock) + goto out; + +r5c_check_stripe_cache_usage (conf); +set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); +r5l_wake_reclaim (conf->log,0 ); +wait_event_lock_irq (conf->wait_for_stripe, + !list_empty (conf->inactive_list + hash) && + (atomic_read (&conf->active_stripes) + < (conf->max_nr_stripes *3 /4 ) + || !test_bit (R5_INACTIVE_BLOCKED , + &conf->cache_state)), + *(conf->hash_locks + hash)); +clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); + goto retry; + +out:spin_unlock_irq (conf->hash_locks + hash);return sh; }
Signature · 1 line
2.30.2
Re: [PATCH 1/5] md/raid5: Refactor raid5_get_active_stripe()
Quoted 7 lines · Logan Gunthorpe
Refactor the
raid5_get_active_stripe()to read more linearly in the order it's typically executed.The
init_stripe()call is called if a free stripe is found and the function is exited early which removes a lot of if (sh) checks and unindents the following code.
Quoted 7 lines
Remove the while loop in favour of the 'goto retry' pattern, which reduces indentation further. And use a 'goto
wait_for_stripe' instead of an additional indent seeing it is the unusual path and this makes the code easier to read.No functional changes intended. Will make subsequent changes in patches easier to understand.
I find the new loop even more confusing than the old one. I'd go with something like the version below (on top of the whol md-next tree that pulled this in way too fast..)
drivers/md/raid5.c +41 -41
@@ -811,54 +811,54 @@ static struct stripe_head *__raid5_get_active_stripe(struct r5conf *conf,spin_lock_irq (conf->hash_locks + hash); -retry: -if (!noquiesce && conf->quiesce) { -/* -* Must release the reference to batch_last before waiting, -* on quiesce, otherwise the batch_last will hold a reference -* to a stripe and raid5_quiesce() will deadlock waiting for -* active_stripes to go to zero. -*/ -if (ctx && ctx->batch_last) { -raid5_release_stripe (ctx->batch_last); - ctx->batch_last =NULL ; - } - -wait_event_lock_irq (conf->wait_for_quiescent, !conf->quiesce, - *(conf->hash_locks + hash)); - } +for (;;) { +if (!noquiesce && conf->quiesce) { +/* +* Must release the reference to batch_last before +* waiting on quiesce, otherwise the batch_last will +* hold a reference to a stripe and raid5_quiesce() +* will deadlock waiting for active_stripes to go to +* zero. +*/ +if (ctx && ctx->batch_last) { +raid5_release_stripe (ctx->batch_last); + ctx->batch_last =NULL ; + } - sh =find_get_stripe (conf, sector, conf->generation - previous, hash); -if (sh) - goto out; +wait_event_lock_irq (conf->wait_for_quiescent, + !conf->quiesce, + *(conf->hash_locks + hash)); + } -if (test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) - goto wait_for_stripe; + sh =find_get_stripe (conf, sector, conf->generation - previous, + hash); +if (sh) +break ; - sh =get_free_stripe (conf, hash); -if (sh) { -r5c_check_stripe_cache_usage (conf); -init_stripe (sh, sector, previous); -atomic_inc (&sh->count); - goto out; - } +if (!test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) { + sh =get_free_stripe (conf, hash); +if (sh) { +r5c_check_stripe_cache_usage (conf); +init_stripe (sh, sector, previous); +atomic_inc (&sh->count); +break ; + } -if (!test_bit (R5_DID_ALLOC , &conf->cache_state)) -set_bit (R5_ALLOC_MORE , &conf->cache_state); +if (!test_bit (R5_DID_ALLOC , &conf->cache_state)) +set_bit (R5_ALLOC_MORE , &conf->cache_state); + } -wait_for_stripe: -if (noblock) - goto out; +if (noblock) +break ; -set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); -r5l_wake_reclaim (conf->log,0 ); -wait_event_lock_irq (conf->wait_for_stripe, -is_inactive_blocked (conf, hash), - *(conf->hash_locks + hash)); -clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); - goto retry; +set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); +r5l_wake_reclaim (conf->log,0 ); +wait_event_lock_irq (conf->wait_for_stripe, +is_inactive_blocked (conf, hash), + *(conf->hash_locks + hash)); +clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); + } -out:spin_unlock_irq (conf->hash_locks + hash);return sh; }
Song Liu
maintainerRe: [PATCH 1/5] md/raid5: Refactor raid5_get_active_stripe()
Quoted 14 lines · Christoph Hellwig
Quoted 12 lines · Logan Gunthorpe
Refactor the
raid5_get_active_stripe()to read more linearly in the order it's typically executed.The
init_stripe()call is called if a free stripe is found and the function is exited early which removes a lot of if (sh) checks and unindents the following code.Remove the while loop in favour of the 'goto retry' pattern, which reduces indentation further. And use a 'goto
wait_for_stripe' instead of an additional indent seeing it is the unusual path and this makes the code easier to read.
Quoted 6 lines
Quoted 2 lines
No functional changes intended. Will make subsequent changes in patches easier to understand.
I find the new loop even more confusing than the old one. I'd go with something like the version below (on top of the whol md-next tree that pulled this in way too fast..)
This looks good to me. Christoph, would you mind send official patch for this?
Thanks,
Song
Quoted 101 lines
drivers/md/raid5.c +41
-41@@ -811,54 +811,54 @@ static struct stripe_head *__raid5_get_active_stripe(struct r5conf *conf,spin_lock_irq (conf->hash_locks + hash); -retry: -if (!noquiesce && conf->quiesce) { -/* -* Must release the reference to batch_last before waiting, -* on quiesce, otherwise the batch_last will hold a reference -* to a stripe and raid5_quiesce() will deadlock waiting for -* active_stripes to go to zero. -*/ -if (ctx && ctx->batch_last) { -raid5_release_stripe (ctx->batch_last); - ctx->batch_last =NULL ; - } - -wait_event_lock_irq (conf->wait_for_quiescent, !conf->quiesce, - *(conf->hash_locks + hash)); - } +for (;;) { +if (!noquiesce && conf->quiesce) { +/* +* Must release the reference to batch_last before +* waiting on quiesce, otherwise the batch_last will +* hold a reference to a stripe and raid5_quiesce() +* will deadlock waiting for active_stripes to go to +* zero. +*/ +if (ctx && ctx->batch_last) { +raid5_release_stripe (ctx->batch_last); + ctx->batch_last =NULL ; + } - sh =find_get_stripe (conf, sector, conf->generation - previous, hash); -if (sh) - goto out; +wait_event_lock_irq (conf->wait_for_quiescent, + !conf->quiesce, + *(conf->hash_locks + hash)); + } -if (test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) - goto wait_for_stripe; + sh =find_get_stripe (conf, sector, conf->generation - previous, + hash); +if (sh) +break ; - sh =get_free_stripe (conf, hash); -if (sh) { -r5c_check_stripe_cache_usage (conf); -init_stripe (sh, sector, previous); -atomic_inc (&sh->count); - goto out; - } +if (!test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) { + sh =get_free_stripe (conf, hash); +if (sh) { +r5c_check_stripe_cache_usage (conf); +init_stripe (sh, sector, previous); +atomic_inc (&sh->count); +break ; + } -if (!test_bit (R5_DID_ALLOC , &conf->cache_state)) -set_bit (R5_ALLOC_MORE , &conf->cache_state); +if (!test_bit (R5_DID_ALLOC , &conf->cache_state)) +set_bit (R5_ALLOC_MORE , &conf->cache_state); + } -wait_for_stripe: -if (noblock) - goto out; +if (noblock) +break ; -set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); -r5l_wake_reclaim (conf->log,0 ); -wait_event_lock_irq (conf->wait_for_stripe, -is_inactive_blocked (conf, hash), - *(conf->hash_locks + hash)); -clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); - goto retry; +set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); +r5l_wake_reclaim (conf->log,0 ); +wait_event_lock_irq (conf->wait_for_stripe, +is_inactive_blocked (conf, hash), + *(conf->hash_locks + hash)); +clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); + } -out:spin_unlock_irq (conf->hash_locks + hash);return sh; }
Re: [PATCH 1/5] md/raid5: Refactor raid5_get_active_stripe()
Quoted 22 lines · Song Liu
Quoted 14 lines · Christoph Hellwig
Quoted 12 lines · Logan Gunthorpe
Refactor the
raid5_get_active_stripe()to read more linearly in the order it's typically executed.The
init_stripe()call is called if a free stripe is found and the function is exited early which removes a lot of if (sh) checks and unindents the following code.Remove the while loop in favour of the 'goto retry' pattern, which reduces indentation further. And use a 'goto
wait_for_stripe' instead of an additional indent seeing it is the unusual path and this makes the code easier to read.Quoted 6 lines
Quoted 2 lines
No functional changes intended. Will make subsequent changes in patches easier to understand.
I find the new loop even more confusing than the old one. I'd go with something like the version below (on top of the whol md-next tree that pulled this in way too fast..)
Quoted 5 lines
This looks good to me. Christoph, would you mind send official patch for this?
Thanks,
Song
I'm on vacation this week, but I'd be happy to send patches addressing Christoph's feedback when I'm back next week.
Thanks,
Logan
Song Liu
maintainerRe: [PATCH 1/5] md/raid5: Refactor raid5_get_active_stripe()
Quoted 26 lines · Logan Gunthorpe
Quoted 22 lines · Song Liu
Quoted 20 lines · Christoph Hellwig
Quoted 7 lines · Logan Gunthorpe
Refactor the
raid5_get_active_stripe()to read more linearly in the order it's typically executed.The
init_stripe()call is called if a free stripe is found and the function is exited early which removes a lot of if (sh) checks and unindents the following code.Quoted 7 lines
Remove the while loop in favour of the 'goto retry' pattern, which reduces indentation further. And use a 'goto
wait_for_stripe' instead of an additional indent seeing it is the unusual path and this makes the code easier to read.No functional changes intended. Will make subsequent changes in patches easier to understand.
I find the new loop even more confusing than the old one. I'd go with something like the version below (on top of the whol md-next tree that pulled this in way too fast..)
Quoted 7 lines
Quoted 5 lines
This looks good to me. Christoph, would you mind send official patch for this?
Thanks,
SongI'm on vacation this week, but I'd be happy to send patches addressing Christoph's feedback when I'm back next week.
We are in the merge window right now. So the timing is a little tricky. I will try to send pull requests with this set as-is. Then we can do follow-ups.
Thanks,
Song
Re: [PATCH 1/5] md/raid5: Refactor raid5_get_active_stripe()
Quoted 2 lines · Song Liu
We are in the merge window right now. So the timing is a little tricky. I will try to send pull requests with this set as-is. Then we can do follow-ups.
I can send the patch. I don't think it's anywhere near critical enought to rush it into the current merge window, though.
Song Liu
maintainerRe: [PATCH 1/5] md/raid5: Refactor raid5_get_active_stripe()
Quoted 7 lines · Christoph Hellwig
Quoted 2 lines · Song Liu
We are in the merge window right now. So the timing is a little tricky. I will try to send pull requests with this set as-is. Then we can do follow-ups.
I can send the patch. I don't think it's anywhere near critical enought to rush it into the current merge window, though.
Agreed. Let's improve it in 6.0.
Thanks!
Song
PATCH 2/5 md/raid5: Make is_inactive_blocked() helper
In reply to Logan GunthorpeThe logic to wait_for_stripe is difficult to parse being on so many lines and with confusing operator precedence. Move it to a helper function to make it easier to read.
No functional changes intended.
--- drivers/md/raid5.c | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-)
drivers/md/raid5.c +19 -5
@@ -755,6 +755,24 @@ static bool has_failed(struct r5conf *conf)return degraded > conf->max_degraded; } +/* +* Block until another thread clears R5_INACTIVE_BLOCKED or +* there are fewer than 3/4 the maximum number of active stripes +* and there is an inactive stripe available. +*/ +static bool is_inactive_blocked (struct r5conf *conf,int hash) +{ +int active =atomic_read (&conf->active_stripes); + +if (list_empty (conf->inactive_list + hash)) +return false; + +if (!test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) +return true; + +return active < (conf->max_nr_stripes *3 /4 ); +} +struct stripe_head *raid5_get_active_stripe (struct r5conf *conf,sector_t sector,int previous,int noblock,int noquiesce)
@@ -796,11 +814,7 @@ raid5_get_active_stripe(struct r5conf *conf, sector_t sector,set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state);r5l_wake_reclaim (conf->log,0 );wait_event_lock_irq (conf->wait_for_stripe, - !list_empty (conf->inactive_list + hash) && - (atomic_read (&conf->active_stripes) - < (conf->max_nr_stripes *3 /4 ) - || !test_bit (R5_INACTIVE_BLOCKED , - &conf->cache_state)), +is_inactive_blocked (conf, hash), *(conf->hash_locks + hash));clear_bit (R5_INACTIVE_BLOCKED , &conf->cache_state); goto retry;
Signature · 1 line
2.30.2
Re: [PATCH 2/5] md/raid5: Make is_inactive_blocked() helper
drivers/md/raid5.c static bool has_failed(struct r5conf *conf) · line 773
Quoted 9 lines · Logan Gunthorpe
drivers/md/raid5.c +9
-0+int active =atomic_read (&conf->active_stripes); + +if (list_empty (conf->inactive_list + hash)) +return false; + +if (!test_bit (R5_INACTIVE_BLOCKED , &conf->cache_state)) +return true; + +return active < (conf->max_nr_stripes *3 /4 );
Wy does this reed ->active_stripes without even knowing if that is needed? In fact I don't see the point of the local active variable at all.
PATCH 3/5 md/raid5: Drop unnecessary call to r5c_check_stripe_cache_usage()
In reply to Logan GunthorpeNow that raid5_get_active_stripe() has been refactored it is appearant that r5c_check_stripe_cache_usage() doesn't need to be called in the wait_for_stripe branch.
r5c_check_stripe_cache_usage() will only conditionally call r5l_wake_reclaim(), but that function is called two lines later.
Drop the call for cleanup.
--- drivers/md/raid5.c | 1 - 1 file changed, 1 deletion(-)
drivers/md/raid5.c +0 -1
@@ -810,7 +810,6 @@ raid5_get_active_stripe(struct r5conf *conf, sector_t sector,if (noblock) goto out; -r5c_check_stripe_cache_usage (conf);set_bit (R5_INACTIVE_BLOCKED , &conf->cache_state);r5l_wake_reclaim (conf->log,0 ); wait_event_lock_irq(conf->wait_for_stripe,
Signature · 1 line
2.30.2
PATCH 4/5 md/raid5: Move stripe_request_ctx up
In reply to Logan GunthorpeMove stripe_request_ctx up. No functional changes intended.
This will be necessary in the next patch to release the batch_last in the context before sleeping.
--- drivers/md/raid5.c | 54 +++++++++++++++++++++++----------------------- 1 file changed, 27 insertions(+), 27 deletions(-)
drivers/md/raid5.c +27 -27
@@ -755,6 +755,33 @@ static bool has_failed(struct r5conf *conf)return degraded > conf->max_degraded; } +enum stripe_result { +STRIPE_SUCCESS =0 , +STRIPE_RETRY , +STRIPE_SCHEDULE_AND_RETRY , +STRIPE_FAIL , +}; + +struct stripe_request_ctx { +/* a reference to the last stripe_head for batching */ +struct stripe_head *batch_last; + +/* first sector in the request */ +sector_t first_sector; + +/* last sector in the request */ +sector_t last_sector; + +/* +* bitmap to track stripe sectors that have been added to stripes +* add one to account for unaligned requests +*/ + DECLARE_BITMAP(sectors_to_do, RAID5_MAX_REQ_STRIPES + 1); + +/* the request had REQ_PREFLUSH, cleared after the first stripe_head */ +bool do_flush; +}; +/* * Block until another thread clears R5_INACTIVE_BLOCKED or * there are fewer than 3/4 the maximum number of active stripes
@@ -5874,33 +5901,6 @@ static bool stripe_ahead_of_reshape(struct mddev *mddev, struct r5conf *conf,return ret; } -enum stripe_result { -STRIPE_SUCCESS =0 , -STRIPE_RETRY , -STRIPE_SCHEDULE_AND_RETRY , -STRIPE_FAIL , -}; - -struct stripe_request_ctx { -/* a reference to the last stripe_head for batching */ -struct stripe_head *batch_last; - -/* first sector in the request */ -sector_t first_sector; - -/* last sector in the request */ -sector_t last_sector; - -/* -* bitmap to track stripe sectors that have been added to stripes -* add one to account for unaligned requests -*/ - DECLARE_BITMAP(sectors_to_do, RAID5_MAX_REQ_STRIPES + 1); - -/* the request had REQ_PREFLUSH, cleared after the first stripe_head */ -bool do_flush; -}; -static int add_all_stripe_bios (struct r5conf *conf,struct stripe_request_ctx *ctx,struct stripe_head *sh,struct bio *bi,int forwrite,int previous)
Signature · 1 line
2.30.2
PATCH 5/5 md/raid5: Ensure batch_last is released before sleeping for quiesce
In reply to Logan GunthorpeA race condition exists where if raid5_quiesce() is called in the middle of a request that has set batch_last, it will deadlock.
batch_last will hold a reference to a stripe when raid5_quiesce() is called. This will cause the next raid5_get_active_stripe() call to sleep waiting for the quiesce to finish, but the raid5_quiesce() thread will wait for active_stripes to go to zero which will never happen because request thread is waiting for the quiesce to stop.
Fix this by creating a special __raid5_get_active_stripe() function which takes the request context and clears the last_batch before sleeping.
While we're at it, change the arguments of raid5_get_active_stripe() to bools.
--- drivers/md/raid5.c | 36 ++++++++++++++++++++++++++++-------- drivers/md/raid5.h | 2 +- 2 files changed, 29 insertions(+), 9 deletions(-)
drivers/md/raid5.c +28 -8
@@ -800,9 +800,9 @@ static bool is_inactive_blocked(struct r5conf *conf, int hash)return active < (conf->max_nr_stripes *3 /4 ); } -struct stripe_head * -raid5_get_active_stripe (struct r5conf *conf,sector_t sector, -int previous,int noblock,int noquiesce) +static struct stripe_head *__raid5_get_active_stripe (struct r5conf *conf, +struct stripe_request_ctx *ctx,sector_t sector, +bool previous,bool noblock,bool noquiesce) {struct stripe_head *sh;int hash =stripe_hash_locks_hash (conf, sector);
@@ -812,9 +812,22 @@ raid5_get_active_stripe(struct r5conf *conf, sector_t sector,spin_lock_irq (conf->hash_locks + hash); retry: -wait_event_lock_irq (conf->wait_for_quiescent, - conf->quiesce ==0 || noquiesce, - *(conf->hash_locks + hash)); +if (!noquiesce && conf->quiesce) { +/* +* Must release the reference to batch_last before waiting, +* on quiesce, otherwise the batch_last will hold a reference +* to a stripe and raid5_quiesce() will deadlock waiting for +* active_stripes to go to zero. +*/ +if (ctx && ctx->batch_last) { +raid5_release_stripe (ctx->batch_last); + ctx->batch_last =NULL ; + } + +wait_event_lock_irq (conf->wait_for_quiescent, !conf->quiesce, + *(conf->hash_locks + hash)); + } + sh =find_get_stripe (conf, sector, conf->generation - previous, hash);if (sh) goto out;
@@ -850,6 +863,13 @@ raid5_get_active_stripe(struct r5conf *conf, sector_t sector,return sh; } +struct stripe_head *raid5_get_active_stripe (struct r5conf *conf, +sector_t sector,bool previous,bool noblock,bool noquiesce) +{ +return __raid5_get_active_stripe (conf,NULL , sector, previous, noblock, + noquiesce); +} +static bool is_full_stripe_write (struct stripe_head *sh) {BUG_ON (sh->overwrite_disks > (sh->disks - sh->raid_conf->max_degraded));
@@ -5992,8 +6012,8 @@ static enum stripe_result make_stripe_request(struct mddev *mddev,pr_debug ("raid456: %s, sector %llu logical %llu\n" , __func__, new_sector, logical_sector); - sh =raid5_get_active_stripe (conf, new_sector, previous, - (bi->bi_opf &REQ_RAHEAD ),0 ); + sh =__raid5_get_active_stripe (conf, ctx, new_sector, previous, + (bi->bi_opf &REQ_RAHEAD ),0 );if (unlikely (!sh)) {/* cannot get stripe, just give-up */ bi->bi_status =BLK_STS_IOERR ;
drivers/md/raid5.h +1 -1
@@ -812,7 +812,7 @@ extern sector_t raid5_compute_sector(struct r5conf *conf, sector_t r_sector, struct stripe_head *sh);extern struct stripe_head *raid5_get_active_stripe (struct r5conf *conf,sector_t sector, -int previous,int noblock,int noquiesce); +bool previous,bool noblock,bool noquiesce);extern int raid5_calc_degraded (struct r5conf *conf);extern int r5c_journal_mode_set (struct mddev *mddev,int journal_mode);#endif
Signature · 1 line
2.30.2
Re: [PATCH 5/5] md/raid5: Ensure batch_last is released before sleeping for quiesce
drivers/md/raid5.c static bool is_inactive_blocked(struct r5conf *conf, int hash) · line 805
Quoted 3 lines · Logan Gunthorpe
drivers/md/raid5.c +3
-0+static struct stripe_head *__raid5_get_active_stripe (struct r5conf *conf, +struct stripe_request_ctx *ctx,sector_t sector, +bool previous,bool noblock,bool noquiesce)
Passing three different bool arguments right after another is a really confusing calling convention, at some point this should become a set of flags. I'd also drop the __raid5_get_active_stripe vs raid5_get_active_stripe distinction.
Quoted 9 lines · Logan Gunthorpe
Hey,
We hit another bug on my recent batching patch. In this case the bug has never been hit with the current md/md-next branch but some other patches we were working on changed the timing such that we hit this bug. It is theoretically possible to hit in the md/md-next batch so this patchset contains a fix.
Quoted 6 lines
The fix is the last commit. The first four commits are some basic refactoring that makes the final commit a bit easier.
A git repo is here and is based on current md/md-next (
7a6f9e9cf1):https://github.com/sbates130272/linux-p2pmem raid5_batch_quiesce
Applied to md-next. Thanks!
Song