aboutsummaryrefslogtreecommitdiff
path: root/drivers/char/random.c
diff options
context:
space:
mode:
authorGravatar Ming Lei <ming.lei@redhat.com> 2022-03-18 21:01:43 +0800
committerGravatar Jens Axboe <axboe@kernel.dk> 2022-03-18 09:57:56 -0600
commit0a9a25ca78437b39e691bcc3dc8240455b803d8d (patch)
treef5e4003404e754f63212e1ed349f7812e5af709c /drivers/char/random.c
parentblock: avoid use-after-free on throttle data (diff)
downloadlinux-0a9a25ca78437b39e691bcc3dc8240455b803d8d.tar.gz
linux-0a9a25ca78437b39e691bcc3dc8240455b803d8d.tar.bz2
linux-0a9a25ca78437b39e691bcc3dc8240455b803d8d.zip
block: let blkcg_gq grab request queue's refcnt
In the whole lifetime of blkcg_gq instance, ->q will be referred, such as, ->pd_free_fn() is called in blkg_free, and throtl_pd_free() still may touch the request queue via &tg->service_queue.pending_timer which is handled by throtl_pending_timer_fn(), so it is reasonable to grab request queue's refcnt by blkcg_gq instance. Previously blkcg_exit_queue() is called from blk_release_queue, and it is hard to avoid the use-after-free. But recently commit 1059699f87eb ("block: move blkcg initialization/destroy into disk allocation/release handler") is merged to for-5.18/block, it becomes simple to fix the issue by simply grabbing request queue's refcnt. Reported-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Ming Lei <ming.lei@redhat.com> Link: https://lore.kernel.org/r/20220318130144.1066064-3-ming.lei@redhat.com Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'drivers/char/random.c')
0 files changed, 0 insertions, 0 deletions