[PATCH] drm/i915: Fix possible null pointer dereference after drm_dbg_printer conversion
Tvrtko Ursulin
tvrtko.ursulin at linux.intel.com
Tue Feb 20 13:45:55 UTC 2024
On 20/02/2024 10:36, Maxime Ripard wrote:
> On Tue, Feb 20, 2024 at 09:16:43AM +0000, Tvrtko Ursulin wrote:
>>
>> On 19/02/2024 20:02, Rodrigo Vivi wrote:
>>> On Mon, Feb 19, 2024 at 01:14:23PM +0000, Tvrtko Ursulin wrote:
>>>> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
>>>>
>>>> Request can be NULL if no guilty request was identified so simply use
>>>> engine->i915 instead.
>>>>
>>>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
>>>> Fixes: d50892a9554c ("drm/i915: switch from drm_debug_printer() to device specific drm_dbg_printer()")
>>>> Reported-by: Dan Carpenter <dan.carpenter at linaro.org>
>>>> Cc: Jani Nikula <jani.nikula at intel.com>
>>>> Cc: Luca Coelho <luciano.coelho at intel.com>
>>>> Cc: Maxime Ripard <mripard at kernel.org>
>>>> Cc: Jani Nikula <jani.nikula at linux.intel.com>
>>>
>>> Reviewed-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
>>
>> Thanks Rodrigo!
>>
>> Given how d50892a9554c landed via drm-misc-next, Maxime or Thomas - could
>> you take this via drm-misc-next-fixes or if there will be another
>> drm-misc-next pull request?
>
> There will be a drm-misc-next PR on thursday
Could you pull this one into which branch is needed so it appears in
that pull request?
Regards,
Tvrtko
More information about the Intel-gfx
mailing list