aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/gcc-plugins/sancov_plugin.c
diff options
context:
space:
mode:
authorMing Lei <[email protected]>2017-02-22 10:14:00 +0000
committerJens Axboe <[email protected]>2017-03-08 16:56:12 +0000
commit7ea5fe31c12dd8bcf4a9c5a4a7e8e23826a9a3b8 (patch)
tree6a9e862fb8ceccf5c64663630d5c2df1f5535656 /scripts/gcc-plugins/sancov_plugin.c
parentblk-mq: initialize mq kobjects in blk_mq_init_allocated_queue() (diff)
downloadkernel-7ea5fe31c12dd8bcf4a9c5a4a7e8e23826a9a3b8.tar.gz
kernel-7ea5fe31c12dd8bcf4a9c5a4a7e8e23826a9a3b8.zip
blk-mq: make lifetime consitent between q/ctx and its kobject
Currently from kobject view, both q->mq_kobj and ctx->kobj can be released during one cycle of blk_mq_register_dev() and blk_mq_unregister_dev(). Actually, sw queue's lifetime is same with its request queue's, which is covered by request_queue->kobj. So we don't need to call kobject_put() for the two kinds of kobject in __blk_mq_unregister_dev(), instead we do that in release handler of request queue. Signed-off-by: Ming Lei <[email protected]> Tested-by: Peter Zijlstra (Intel) <[email protected]> Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'scripts/gcc-plugins/sancov_plugin.c')
0 files changed, 0 insertions, 0 deletions