Linux Kernel wave5 VPU driver: Fix spinlock deadlock in handle_dynamic_resolution_change

Vulnerability Summary Overview Title: media: chips-media: wave5: Fix Reports from Kernel Lock Validator Type: Kernel lock contention / Deadlock risk (Lock Validator report) Description: In the function, the code attempts to acquire a . However, this function may be invoked in a context where the lock is already held (e.g., via the call chain), leading to a deadlock or triggering errors from the lock validator. Specifically, functions such as and do not correctly check the lock state before invocation, or they attempt to reacquire the lock within a context where it is already held. Scope of Impact Subsystem: Linux Kernel Media Subsystem (V4L2) Driver: (Wave5 VPU driver) File: Affected Functions: - - - - Remediation Strategy Core Concept: Decouple operations that require acquiring the lock from the "lock-held context," or ensure the lock is not held prior to invocation. Specific Modifications: 1. Introduce Auxiliary Functions/Variables: - In , instead of directly modifying , pass the data via the structure, or ensure the function is invoked in a safe context. - In , remove the logic for directly acquiring the , and instead rely on an event mechanism or ensure the caller already holds the lock. 2. Code Change Details: - : - Original Code: Directly modified . - New Code: Passes via the structure, handling lock acquisition and modification uniformly in . - : - Removed internal and . - Directly modifies , assuming the caller already holds the lock (or acquires it before the call). - Caller Modifications: - In and , explicitly acquire the before calling , and release it afterward. - Example: 3. Initialization Fix: - In , point the function pointer to a new function that initializes fields such as , ensuring state consistency. Key Code Changes (Diff Summary)

Goal Reached Thanks to every supporter — we hit 100%!

Linux Kernel wave5 VPU driver: Fix spinlock deadlock in handle_dynamic_resolution_change