diff options
| author | Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com> | 2026-07-10 10:15:18 +0000 |
|---|---|---|
| committer | Yu Kuai <yukuai@fygo.io> | 2026-07-30 23:33:35 +0800 |
| commit | addb977450a662e1961d272b6ebfcb477d115044 (patch) | |
| tree | 1e93cb232833bf8df01278a59fd5646d13350c05 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | 3409bf2f9678d769a4c33bd232a3571c51fac481 (diff) | |
md/raid10: remove unnecessary barrier around bio_submit_split_bioset()
raid10_write_request() drops the barrier before calling
bio_submit_split_bioset() and reacquires it afterwards. This is no
longer necessary because the split bio cannot re-enter
raid10_write_request() while the barrier is held.
The allow_barrier()/wait_barrier() pair was introduced by commit
e820d55cb99d ("md: fix raid10 hang issue caused by barrier") when
submit_flushes() called md_handle_request() directly, allowing re-entry
into raid10_write_request(). Since v5.2, submit_flushes() has instead
gone through submit_bio(), eliminating that recursion. submit_flushes()
was later removed entirely by commit b75197e86e6d ("md: Remove flush
handling").
Currently, raid10_write_request() is only entered from the bio
submission path, so the split bio submitted by bio_submit_split_bioset()
cannot recurse back into wait_barrier().
Remove the redundant allow_barrier()/wait_barrier() pair around
bio_submit_split_bioset().
Signed-off-by: Abd-Alrhman Masalkhi <abd.masalkhi@gmail.com>
Reviewed-by: Yu Kuai <yukuai@fygo.io>
Link: https://patch.msgid.link/20260710101521.1714-5-abd.masalkhi@gmail.com
Signed-off-by: Yu Kuai <yukuai@fygo.io>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions
