diff options
| author | Logan Gunthorpe <logang@deltatee.com> | 2022-06-08 10:27:51 -0600 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2022-08-02 17:14:31 -0600 |
| commit | 7769085c8d4d7aad4e68f2f4f2077bd46449511f (patch) | |
| tree | 69312769f828206bc29df5dc90125056bca17131 /tools/perf/scripts/python/flamegraph.py | |
| parent | md/raid5-cache: Take mddev_lock in r5c_journal_mode_show() (diff) | |
| download | linux-7769085c8d4d7aad4e68f2f4f2077bd46449511f.tar.gz linux-7769085c8d4d7aad4e68f2f4f2077bd46449511f.zip | |
md/raid5-cache: Drop RCU usage of conf->log
The only place that uses RCU to access conf->log is in
r5l_log_disk_error(). This function is mostly used in the IO path
and once with mddev_lock() held in raid5_change_consistency_policy().
It is known that the IO will be suspended before the log is freed and
r5l_log_exit() is called with the mddev_lock() held.
This should mean that conf->log can not be freed while the function is
being called, so the RCU protection is not necessary. Drop the
rcu_read_lock() as well as the synchronize_rcu() and
rcu_assign_pointer() usage.
Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Song Liu <song@kernel.org>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions