aboutsummaryrefslogtreecommitdiffstats
path: root/tools/lib/bpf/linker.c
diff options
context:
space:
mode:
authorMing Lei <[email protected]>2025-04-03 10:54:02 +0000
committerJens Axboe <[email protected]>2025-04-03 14:32:03 +0000
commit01b91bf14f6d4893e03e357006e7af3a20c03fee (patch)
tree5cf0164c47d301865c47bb10938a59ad0ec143e5 /tools/lib/bpf/linker.c
parentMerge tag 'nvme-6.15-2025-04-02' of git://git.infradead.org/nvme into block-6.15 (diff)
downloadkernel-01b91bf14f6d4893e03e357006e7af3a20c03fee.tar.gz
kernel-01b91bf14f6d4893e03e357006e7af3a20c03fee.zip
block: don't grab elevator lock during queue initialization
->elevator_lock depends on queue freeze lock, see block/blk-sysfs.c. queue freeze lock depends on fs_reclaim. So don't grab elevator lock during queue initialization which needs to call kmalloc(GFP_KERNEL), and we can cut the dependency between ->elevator_lock and fs_reclaim, then the lockdep warning can be killed. This way is safe because elevator setting isn't ready to run during queue initialization. There isn't such issue in __blk_mq_update_nr_hw_queues() because memalloc_noio_save() is called before acquiring elevator lock. Fixes the following lockdep warning: https://lore.kernel.org/linux-block/[email protected]/ Reported-by: [email protected] Cc: Nilay Shroff <[email protected]> Signed-off-by: Ming Lei <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/lib/bpf/linker.c')
0 files changed, 0 insertions, 0 deletions