aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy-src.c
diff options
context:
space:
mode:
authorLi Lingfeng <[email protected]>2023-08-10 11:51:11 +0800
committerJens Axboe <[email protected]>2023-08-10 07:20:31 -0600
commit4eb44d10766ac0fae5973998fd2a0103df1d3fe1 (patch)
tree2580c861923412ef148897924352d347cdec321a /lib/test_fortify/write_overflow-strncpy-src.c
parentc8659bbb15cd42577a9b16a23b527436b028c8b2 (diff)
block: remove init_mutex and open-code blk_iolatency_try_init
Commit a13696b83da4 ("blk-iolatency: Make initialization lazy") adds a mutex named "init_mutex" in blk_iolatency_try_init for the race condition of initializing RQ_QOS_LATENCY. Now a new lock has been add to struct request_queue by commit a13bd91be223 ("block/rq_qos: protect rq_qos apis with a new lock"). And it has been held in blkg_conf_open_bdev before calling blk_iolatency_init. So it's not necessary to keep init_mutex in blk_iolatency_try_init, just remove it. Since init_mutex has been removed, blk_iolatency_try_init can be open-coded back to iolatency_set_limit() like ioc_qos_write(). Signed-off-by: Li Lingfeng <[email protected]> Reviewed-by: Michal Koutný <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions