On Tue, 26 Aug 2025 11:18:57 -0300, Maíra Canal wrote:
> This patch series was initially motivated by a race condition (exposed
> in PATCH 4/6) where we lacked synchronization for `job->file` access.
> This led to use-after-free issues when a file descriptor was closed
> while a job was still running.
>
> However, beyond fixing this specific race, the series introduces
> broader improvements to active job management and locking. While PATCH
> 1/6, 2/6, and 5/6 are primarily code refactors, PATCH 3/6 brings a
> significant change to the locking scheme. Previously, all queues shared
> the same spinlock, which caused unnecessary contention during high GPU
> usage across different queues. PATCH 3/6 allows queues to operate more
> independently.
>
> [...]
Applied, thanks!
[1/6] drm/v3d: Store a pointer to `struct v3d_file_priv` inside each job
commit: e5e3d7bff7645d2577c56ccc8b110b9b6978aa08
[2/6] drm/v3d: Store the active job inside the queue's state
commit: 0d3768826d38c0ac740f8b45cd13346630535f2b
[3/6] drm/v3d: Replace a global spinlock with a per-queue spinlock
commit: e9d8e027483267a9505f5b6b7f0476b5299743af
[4/6] drm/v3d: Address race-condition between per-fd GPU stats and fd release
commit: fa6a20c8747041df406d184321a2a49e82d46298
[5/6] drm/v3d: Synchronous operations can't timeout
commit: 78fe02d090d38393cc00de9d1929e59426f202a4
[6/6] drm/v3d: Protect per-fd reset counter against fd release
commit: 7d9bc9bee2778e2da7147aeb3a81427487598493
Best regards,
- Maíra
