aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow_field-memset.c
diff options
context:
space:
mode:
authorRui Zhang <zr.zhang@vivo.com>2022-12-01 11:38:06 +0800
committerMark Brown <broonie@kernel.org>2022-12-01 11:41:19 +0000
commit0591b14ce0398125439c759f889647369aa616a0 (patch)
treec62333a4f76f1b4555f0491dd08b41460c4da161 /lib/test_fortify/write_overflow_field-memset.c
parentf39f8709c217d82aabbf51d8669731137ce09aea (diff)
regulator: core: fix use_count leakage when handling boot-on
I found a use_count leakage towards supply regulator of rdev with boot-on option. ┌───────────────────┐ ┌───────────────────┐ │ regulator_dev A │ │ regulator_dev B │ │ (boot-on) │ │ (boot-on) │ │ use_count=0 │◀──supply──│ use_count=1 │ │ │ │ │ └───────────────────┘ └───────────────────┘ In case of rdev(A) configured with `regulator-boot-on', the use_count of supplying regulator(B) will increment inside regulator_enable(rdev->supply). Thus, B will acts like always-on, and further balanced regulator_enable/disable cannot actually disable it anymore. However, B was also configured with `regulator-boot-on', we wish it could be disabled afterwards. Signed-off-by: Rui Zhang <zr.zhang@vivo.com> Link: https://lore.kernel.org/r/20221201033806.2567812-1-zr.zhang@vivo.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'lib/test_fortify/write_overflow_field-memset.c')
0 files changed, 0 insertions, 0 deletions