Claude review: drm/atomic: protect bridge private_obj during bridge removal

[Claude Code Review Bot <claude-review@example.com>]

Overall Series Review

Subject: drm/atomic: protect bridge private_obj during bridge removal
Author: Luca Ceresoli <luca.ceresoli@bootlin.com>
Patches: 2
Reviewed: 2026-03-25T06:50:56.340536

---

This is a single-patch series addressing a real race condition in DRM bridge hot-unplug. The problem is well-understood and clearly documented in the commit message: when a bridge's `private_obj` is being finalized via `drm_bridge_detach()` concurrently with code that holds modeset locks (e.g., `drm_mode_obj_get_properties_ioctl()` using `DRM_MODESET_LOCK_ALL_BEGIN/END`), the `drm_modeset_lock_fini()` call hits a `WARN_ON` because the lock is still on the acquire context's locked list.

The fix is minimal and correct: wrap the `list_del(&obj->head)` in `drm_atomic_private_obj_fini()` with `DRM_MODESET_LOCK_ALL_BEGIN/END`. This serializes the list removal against concurrent lock acquisition, ensuring the private object is either fully locked by the concurrent user (who will finish and release before fini proceeds) or removed from the list before the concurrent user iterates it.

The series is well-motivated as part of ongoing DRM bridge hotplug work, and the roadmap in the cover letter is appreciated.

---
Generated by Claude Code Patch Reviewer