summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorMyeonghun Pak <mhun512@gmail.com>2026-10-02 17:44:16 -0400
committerJiri Kosina <jkosina@suse.com>2026-10-16 11:47:45 +0200
commit6a006ff898b459e0bd10375d7fbe0ea7f7a132b9 (patch)
tree71e7128d06ec11fb02cd0acc9c9db5774beeba30 /tools/perf/scripts/python/event_analyzing_sample.py
parent5b66b65cfd6f697b1addb6159cbece53d20db2fc (diff)
HID: mcp2221: always initialize and cancel init_work
The writable gpio_mode_enforce parameter can change between probe and remove. If it changes from false to true after probe, remove skips cancellation of init_work. Pending or running work can then access devm-managed driver state after teardown. Changing it from true to false can make remove cancel an uninitialized delayed work item. Initialize init_work whenever IIO is reachable and cancel it unconditionally on remove. Keep the parameter check only for scheduling the initialization. The false-to-true cancellation gap was previously reported by Sashiko. We also encountered this issue during our static-analysis research. Fixes: 200e6c6e94fa ("HID: mcp2221: Add module parameter to enfoce GPIO mode") Reported-by: Sashiko <sashiko-bot@kernel.org> Link: https://lore.kernel.org/linux-input/20260715143415.916A21F00A3A@smtp.kernel.org/ Assisted-by: LLM Cc: stable@vger.kernel.org Signed-off-by: Myeonghun Pak <mhun512@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions