drm: move allocation out of drm_get_format_name()
The function's behaviour was changed in90844f0004
, without changing its signature, causing people to keep using it the old way without realising they were now leaking memory. Rob Clark also noticed it was also allocating GFP_KERNEL memory in atomic contexts, breaking them. Instead of having to allocate GFP_ATOMIC memory and fixing the callers to make them cleanup the memory afterwards, let's change the function's signature by having the caller take care of the memory and passing it to the function. The new parameter is a single-field struct in order to enforce the size of its buffer and help callers to correctly manage their memory. Fixes:90844f0004
("drm: make drm_get_format_name thread-safe") Cc: Rob Clark <robdclark@gmail.com> Cc: Christian König <christian.koenig@amd.com> Acked-by: Christian König <christian.koenig@amd.com> Acked-by: Rob Clark <robdclark@gmail.com> Acked-by: Sinclair Yeh <syeh@vmware.com> (vmwgfx) Reviewed-by: Jani Nikula <jani.nikula@intel.com> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Eric Engestrom <eric@engestrom.ch> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Link: http://patchwork.freedesktop.org/patch/msgid/20161112011309.9799-1-eric@engestrom.ch
This commit is contained in:

committed by
Daniel Vetter

parent
f92e1ee52a
commit
b3c11ac267
@@ -75,10 +75,11 @@ void drm_helper_mode_fill_fb_struct(struct drm_framebuffer *fb,
|
||||
|
||||
info = drm_format_info(mode_cmd->pixel_format);
|
||||
if (!info || !info->depth) {
|
||||
char *format_name = drm_get_format_name(mode_cmd->pixel_format);
|
||||
struct drm_format_name_buf format_name;
|
||||
|
||||
DRM_DEBUG_KMS("non-RGB pixel format %s\n", format_name);
|
||||
kfree(format_name);
|
||||
DRM_DEBUG_KMS("non-RGB pixel format %s\n",
|
||||
drm_get_format_name(mode_cmd->pixel_format,
|
||||
&format_name));
|
||||
|
||||
fb->depth = 0;
|
||||
fb->bits_per_pixel = 0;
|
||||
|
Reference in New Issue
Block a user