summaryrefslogtreecommitdiff
path: root/drivers/block
diff options
context:
space:
mode:
authorLin Ma <linma@zju.edu.cn>2022-05-16 12:20:35 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-06-09 11:20:55 +0300
commit1a5a3dfd9f172dcb115072f0aea5e27d3083c20e (patch)
tree6c74e5468ca0c3c0f76aa17b637bab2c1b320858 /drivers/block
parentaf98940dd33c9f9e1beb4f71c0a39260100e2a65 (diff)
downloadlinux-1a5a3dfd9f172dcb115072f0aea5e27d3083c20e.tar.xz
ASoC: rt5645: Fix errorenous cleanup order
[ Upstream commit 2def44d3aec59e38d2701c568d65540783f90f2f ] There is a logic error when removing rt5645 device as the function rt5645_i2c_remove() first cancel the &rt5645->jack_detect_work and delete the &rt5645->btn_check_timer latter. However, since the timer handler rt5645_btn_check_callback() will re-queue the jack_detect_work, this cleanup order is buggy. That is, once the del_timer_sync in rt5645_i2c_remove is concurrently run with the rt5645_btn_check_callback, the canceled jack_detect_work will be rescheduled again, leading to possible use-after-free. This patch fix the issue by placing the del_timer_sync function before the cancel_delayed_work_sync. Signed-off-by: Lin Ma <linma@zju.edu.cn> Link: https://lore.kernel.org/r/20220516092035.28283-1-linma@zju.edu.cn Signed-off-by: Mark Brown <broonie@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/block')
0 files changed, 0 insertions, 0 deletions