diff options
| author |   Ville Syrjälä <ville.syrjala@linux.intel.com> | 2025-10-03 17:57:31 +0300 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-10-23 16:24:33 +0200 |
| commit | dd3fb43ebdb9a23b3ef63d911ea21a3c1916b7fe (patch) | |
| tree | ec257f6a040d2abbc0c72c91c170925e41a96b25 /tools/perf/scripts/python | |
| parent | drm/i915/frontbuffer: Move bo refcounting intel_frontbuffer_{get,release}() (diff) | |
drm/i915/fb: Fix the set_tiling vs. addfb race, again
[ Upstream commit 86af6b90e0556fcefbc6e98eb78bdce90327ee76 ]
intel_frontbuffer_get() is what locks out subsequent set_tiling
changes to the bo. Thus the fence vs. modifier check must be done
after intel_frontbuffer_get(), or else a concurrent set_tiling ioctl
might sneak in and change the fence after the check has been done.
Close the race again. See commit dd689287b977 ("drm/i915: Prevent
concurrent tiling/framebuffer modifications") for the previous
instance.
v2: Reorder intel_user_framebuffer_destroy() to match the unwind (Jani)
Cc: Jouni Högander <jouni.hogander@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Fixes: 10690b8a49bc ("drm/i915/display: Add intel_fb_bo_framebuffer_fini")
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20251003145734.7634-3-ville.syrjala@linux.intel.com
(cherry picked from commit 1d1e4ded216017f8febd91332ee337f0e0e79285)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions