drm: Make sure that encoder_type for drm_encoder_init() is in the list
Subsystems (2)
PATCH 1/1 drm: Make sure that encoder_type for drm_encoder_init() is in the list
If a encoder name isn't specified for drm_encoder_init() it will try to construct one based on the incoming encoder_type identifier. If the caller passes an invalid encoder_type value the lookup could walk right past the end of the table.
--- drivers/gpu/drm/drm_encoder.c | 6 ++++++ 1 file changed, 6 insertions(+)
drivers/gpu/drm/drm_encoder.c +6 -0
@@ -128,6 +128,12 @@ int drm_encoder_init(struct drm_device *dev, encoder->name =kvasprintf (GFP_KERNEL , name, ap);va_end (ap); }else { +/* Make sure that the requested encoder type is in the list */ +if (encoder_type >=ARRAY_SIZE (drm_encoder_enum_list)) { + ret = -EINVAL ; + goto out_put; + } + encoder->name =kasprintf (GFP_KERNEL ,"%s-%d" , drm_encoder_enum_list[encoder_type].name, encoder->base.id);
Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 15 lines · Jordan Crouse
If a encoder name isn't specified for
drm_encoder_init()it will try to construct one based on the incomingencoder_typeidentifier. If the caller passes an invalidencoder_typevalue the lookup could walk right past the end of the table.Signed-off-by Jordan Crouse <[email protected]>--- drivers/gpu/drm/drm_encoder.c | 6 ++++++ 1 file changed, 6 insertions(+)drivers/gpu/drm/drm_encoder.c +0
-0
drivers/gpu/drm/drm_encoder.c int drm_encoder_init(struct drm_device *dev, · line 132
Quoted 5 lines
drivers/gpu/drm/drm_encoder.c +2
-0@@ -128,6 +128,12 @@ int drm_encoder_init(struct drm_device *dev, encoder->name =kvasprintf (GFP_KERNEL , name, ap);va_end (ap); }else { +/* Make sure that the requested encoder type is in the list */ +if (encoder_type >=ARRAY_SIZE (drm_encoder_enum_list)) {
I think moving that to the top and wrapping it in a WARN_ON would be even better - specifying and invalid encoder type is clearly a driver bug. -Daniel
Quoted 14 lines
drivers/gpu/drm/drm_encoder.c +4
-0+ ret = -EINVAL ; + goto out_put; + } + encoder->name =kasprintf (GFP_KERNEL ,"%s-%d" , drm_encoder_enum_list[encoder_type].name, encoder->base.id);Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Quoted 11 lines · Daniel Vetter
Quoted 10 lines · Jordan Crouse
If a encoder name isn't specified for
drm_encoder_init()it will try to construct one based on the incomingencoder_typeidentifier. If the caller passes an invalidencoder_typevalue the lookup could walk right past the end of the table.Signed-off-by Jordan Crouse <[email protected]>--- drivers/gpu/drm/drm_encoder.c | 6 ++++++ 1 file changed, 6 insertions(+)
Quoted 14 lines
drivers/gpu/drm/drm_encoder.c int drm_encoder_init(struct drm_device *dev, · line 132
Quoted 10 lines
drivers/gpu/drm/drm_encoder.c +2
-0@@ -128,6 +128,12 @@ int drm_encoder_init(struct drm_device *dev, encoder->name =kvasprintf (GFP_KERNEL , name, ap);va_end (ap); }else { +/* Make sure that the requested encoder type is in the list */ +if (encoder_type >=ARRAY_SIZE (drm_encoder_enum_list)) {I think moving that to the top and wrapping it in a
WARN_ONwould be even better - specifying and invalid encoder type is clearly a driver bug. -Daniel
It wasn't immediately clear to me if it was legal to pass a "custom" encoder type assuming you provided a name for it so I erred on the side of caution. I would have no problem moving it up to the top and being loud about it.
Jordan
Quoted 19 lines
Quoted 14 lines
drivers/gpu/drm/drm_encoder.c +4
-0+ ret = -EINVAL ; + goto out_put; + } + encoder->name =kasprintf (GFP_KERNEL ,"%s-%d" , drm_encoder_enum_list[encoder_type].name, encoder->base.id);Signature · 6 lines
2.17.1 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-develSignature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Signature · 6 lines
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel