summaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2024-04-06 17:08:21 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2024-05-02 17:35:34 +0300
commit9827caa5105fb16d1fae2e75c8d0e4662014b3ca (patch)
treedddf0b20ed1c38560b5e19dac9aa73aa5e20af55 /init
parentea6628e4e2353978af7e3b4ad4fdaab6149acf3d (diff)
downloadlinux-9827caa5105fb16d1fae2e75c8d0e4662014b3ca.tar.xz
phy: ti: tusb1210: Resolve charger-det crash if charger psy is unregistered
[ Upstream commit bf6e4ee5c43690e4c5a8a057bbcd4ff986bed052 ] The power_supply frame-work is not really designed for there to be long living in kernel references to power_supply devices. Specifically unregistering a power_supply while some other code has a reference to it triggers a WARN in power_supply_unregister(): WARN_ON(atomic_dec_return(&psy->use_cnt)); Folllowed by the power_supply still getting removed and the backing data freed anyway, leaving the tusb1210 charger-detect code with a dangling reference, resulting in a crash the next time tusb1210_get_online() is called. Fix this by only holding the reference in tusb1210_get_online() freeing it at the end of the function. Note this still leaves a theoretical race window, but it avoids the issue when manually rmmod-ing the charger chip driver during development. Fixes: 48969a5623ed ("phy: ti: tusb1210: Add charger detection") Signed-off-by: Hans de Goede <hdegoede@redhat.com> Link: https://lore.kernel.org/r/20240406140821.18624-1-hdegoede@redhat.com Signed-off-by: Vinod Koul <vkoul@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions