drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
Subsystems (4)
PATCH 1/3 drm/i915/fbdev: Fix num_connector references in intel_fb_initial_config()
During boot time, MST devices usually send a ton of hotplug events irregardless of whether or not any physical hotplugs actually occurred. Hotplugs mean connectors being created/destroyed, and the number of DRM connectors changing under us. This isn't a problem if we use fb_helper->connector_count since we only set it once in the code, however if we use num_connector from struct drm_mode_config we risk it's value changing under us. On top of that, there's even a chance that dev->mode_config.num_connector != fb_helper->connector_count. If the number of connectors happens to increase under us, we'll end up using the wrong array size for memcpy and start writing beyond the actual length of the array, occasionally resulting in kernel panics.
--- drivers/gpu/drm/i915/intel_fbdev.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/intel_fbdev.c +3 -3
@@ -366,12 +366,12 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,uint64_t conn_configured =0 , mask;int pass =0 ; - save_enabled =kcalloc (dev->mode_config.num_connector,sizeof (bool ), + save_enabled =kcalloc (fb_helper->connector_count,sizeof (bool ),GFP_KERNEL );if (!save_enabled)return false; -memcpy (save_enabled, enabled, dev->mode_config.num_connector); +memcpy (save_enabled, enabled, fb_helper->connector_count); mask = (1 << fb_helper->connector_count) -1 ; retry:for (i =0 ; i < fb_helper->connector_count; i++) {
@@ -510,7 +510,7 @@ retry:if (fallback) { bail:DRM_DEBUG_KMS ("Not using firmware configuration\n" ); -memcpy (enabled, save_enabled, dev->mode_config.num_connector); +memcpy (enabled, save_enabled, fb_helper->connector_count);kfree (save_enabled);return false; }
Signature · 1 line
2.5.5
PATCH 2/3 drm/fb_helper: Fix references to dev->mode_config.num_connector
During boot, MST hotplugs are generally expected (even if no physical hotplugging occurs) and result in DRM's connector topology changing. This means that using num_connector from the current mode configuration can lead to the number of connectors changing under us. This can lead to some nasty scenarios in fbcon:
- We allocate an array to the size of dev->mode_config.num_connectors.
- MST hotplug occurs, dev->mode_config.num_connectors gets incremented.
- We try to loop through each element in the array using the new value of dev->mode_config.num_connectors, and end up going out of bounds since dev->mode_config.num_connectors is now larger then the array we allocated.
fb_helper->connector_count however, will always remain consistent while we do a modeset in fb_helper.
--- drivers/gpu/drm/drm_fb_helper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/drm_fb_helper.c +2 -2
@@ -1914,7 +1914,7 @@ static int drm_pick_crtcs(struct drm_fb_helper *fb_helper,if (modes[n] ==NULL )return best_score; - crtcs =kzalloc (dev->mode_config.num_connector * + crtcs =kzalloc (fb_helper->connector_count *sizeof (struct drm_fb_helper_crtc *),GFP_KERNEL );if (!crtcs)return best_score;
@@ -1960,7 +1960,7 @@ static int drm_pick_crtcs(struct drm_fb_helper *fb_helper,if (score > best_score) { best_score = score;memcpy (best_crtcs, crtcs, - dev->mode_config.num_connector * + fb_helper->connector_count *sizeof (struct drm_fb_helper_crtc *)); } }
Signature · 6 lines
2.5.5 _______________________________________________ dri-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 2/3] drm/fb_helper: Fix references to dev->mode_config.num_connector
Quoted 13 lines · Lyude
During boot, MST hotplugs are generally expected (even if no physical hotplugging occurs) and result in DRM's connector topology changing. This means that using
num_connectorfrom the current mode configuration can lead to the number of connectors changing under us. This can lead to some nasty scenarios in fbcon:- We allocate an array to the size of
dev->mode_config.num_connectors.
- MST hotplug occurs,dev->mode_config.num_connectorsgets incremented.
- We try to loop through each element in the array using the new value ofdev->mode_config.num_connectors, and end up going out of bounds sincedev->mode_config.num_connectorsis now larger then the array we allocated.
Quoted 5 lines
fb_helper->connector_counthowever, will always remain consistent while we do a modeset infb_helper.Signed-off-by Lyude <[email protected]>
Ok, this one looks like it's indeed in the same critical section (within drm_setup_outputs) as where we allocate the fb helper connector array. So I think this one here is not needed to fix a bug?
Still makes sense as a patch, but not with cc: stable I think. -Daniel
Quoted 33 lines
--- drivers/gpu/drm/drm_fb_helper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)drivers/gpu/drm/drm_fb_helper.c +2
-2@@ -1914,7 +1914,7 @@ static int drm_pick_crtcs(struct drm_fb_helper *fb_helper,if (modes[n] ==NULL )return best_score; - crtcs =kzalloc (dev->mode_config.num_connector * + crtcs =kzalloc (fb_helper->connector_count *sizeof (struct drm_fb_helper_crtc *),GFP_KERNEL );if (!crtcs)return best_score;@@ -1960,7 +1960,7 @@ static int drm_pick_crtcs(struct drm_fb_helper *fb_helper,if (score > best_score) { best_score = score;memcpy (best_crtcs, crtcs, - dev->mode_config.num_connector * + fb_helper->connector_count *sizeof (struct drm_fb_helper_crtc *)); } }Signature · 6 lines
2.5.5 _______________________________________________ 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
Re: [PATCH 2/3] drm/fb_helper: Fix references to dev->mode_config.num_connector
I would Cc it to stable just in case tbh. I picked up on this one since KASAN was picking up on some of the memcpy() calls around here going out of bounds. I can include some of the backtraces from that if needed.
Quoted 64 lines · Daniel Vetter
Quoted 14 lines · Lyude
During boot, MST hotplugs are generally expected (even if no physical hotplugging occurs) and result in DRM's connector topology changing. This means that using
num_connectorfrom the current mode configuration can lead to the number of connectors changing under us. This can lead to some nasty scenarios in fbcon:- We allocate an array to the size of
dev->mode_config.num_connectors.
- MST hotplug occurs,dev->mode_config.num_connectorsgets incremented.
- We try to loop through each element in the array using the new value ofdev->mode_config.num_connectors, and end up going out of bounds sincedev->mode_config.num_connectorsis now larger then the array we allocated.Quoted 5 lines
fb_helper->connector_counthowever, will always remain consistent while we do a modeset infb_helper.Signed-off-by Lyude <[email protected]>Ok, this one looks like it's indeed in the same critical section (within
drm_setup_outputs) as where we allocate the fb helper connector array. So I think this one here is not needed to fix a bug?Still makes sense as a patch, but not with cc: stable I think. -Daniel
Quoted 37 lines
---
drivers/gpu/drm/drm_fb_helper.c | 4 ++--1 file changed, 2 insertions(+), 2 deletions(-)drivers/gpu/drm/drm_fb_helper.c +0
-0@@ -1914,7 +1914,7 @@ static int drm_pick_crtcs(struct drm_fb_helper *fb_helper, if (modes[n] == NULL) return best_score;drivers/gpu/drm/drm_fb_helper.c +1
-1- crtcs = kzalloc(dev->mode_config.num_connector * + crtcs = kzalloc(fb_helper->connector_count *
sizeof(struct drm_fb_helper_crtc *),GFP_KERNEL); if (!crtcs)
returnbest_score;drivers/gpu/drm/drm_fb_helper.c +1
-1@@ -1960,7 +1960,7 @@ static int drm_pick_crtcs(struct drm_fb_helper *fb_helper, if (score > best_score) { best_score = score; memcpy(best_crtcs, crtcs, - dev->mode_config.num_connector * + fb_helper->connector_count * sizeof(struct drm_fb_helper_crtc *)); }}
--
2.5.5_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Signature · 2 lines
Cheers, Lyude
PATCH 3/3 drm/fb_helper: Fix a few typos
In reply to Lyudes/modest/modeset/
s/aftert/after/
--- drivers/gpu/drm/drm_fb_helper.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/gpu/drm/drm_fb_helper.c +3 -3
@@ -2104,8 +2104,8 @@ out:* cmdline option. * * The other option is to just disable fbdev emulation since very likely the -* first modest from userspace will crash in the same way, and is even easier to -* debug. This can be done by setting the drm_kms_helper.fbdev_emulation=0 +* first modeset from userspace will crash in the same way, and is even easier +* to debug. This can be done by setting the drm_kms_helper.fbdev_emulation=0 * kernel cmdline option. * * RETURNS:
@@ -2150,7 +2150,7 @@ EXPORT_SYMBOL(drm_fb_helper_initial_config);* hotplug interrupt). * * Note that drivers may call this even before calling -* drm_fb_helper_initial_config but only aftert drm_fb_helper_init. This allows +* drm_fb_helper_initial_config but only after drm_fb_helper_init. This allows * for a race-free fbcon setup and will make sure that the fbdev emulation will * not miss any hotplug events. *
Signature · 6 lines
2.5.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Daniel Vetter
AppliedRe: [Intel-gfx] [PATCH 3/3] drm/fb_helper: Fix a few typos
Quoted 4 lines · Lyude
s/modest/modeset/
s/aftert/after/Signed-off-by Lyude <[email protected]>
Applied to drm-misc, thanks.
-Daniel
Quoted 35 lines
--- drivers/gpu/drm/drm_fb_helper.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)drivers/gpu/drm/drm_fb_helper.c +3
-3@@ -2104,8 +2104,8 @@ out:* cmdline option. * * The other option is to just disable fbdev emulation since very likely the -* first modest from userspace will crash in the same way, and is even easier to -* debug. This can be done by setting the drm_kms_helper.fbdev_emulation=0 +* first modeset from userspace will crash in the same way, and is even easier +* to debug. This can be done by setting the drm_kms_helper.fbdev_emulation=0 * kernel cmdline option. * * RETURNS: @@ -2150,7 +2150,7 @@ EXPORT_SYMBOL(drm_fb_helper_initial_config);* hotplug interrupt). * * Note that drivers may call this even before calling -* drm_fb_helper_initial_config but only aftert drm_fb_helper_init. This allows +* drm_fb_helper_initial_config but only after drm_fb_helper_init. This allows * for a race-free fbcon setup and will make sure that the fbdev emulation will * not miss any hotplug events. * Signature · 6 lines
2.5.5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 12 lines · Lyude
During boot time, MST devices usually send a ton of hotplug events irregardless of whether or not any physical hotplugs actually occurred. Hotplugs mean connectors being created/destroyed, and the number of DRM connectors changing under us. This isn't a problem if we use
fb_helper->connector_countsince we only set it once in the code, however if we usenum_connectorfrom structdrm_mode_configwe risk it's value changing under us. On top of that, there's even a chance thatdev->mode_config.num_connector!=fb_helper->connector_count. If the number of connectors happens to increase under us, we'll end up using the wrong array size for memcpy and start writing beyond the actual length of the array, occasionally resulting in kernel panics.
Quoted 2 lines
Signed-off-by Lyude <[email protected]>
So at first I thought this is impossible, because we hold the dev->mode_config.mutex in all relevant places. But we drop it in-between, so this can indeed race.
Quoted 10 lines
--- drivers/gpu/drm/i915/intel_fbdev.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)drivers/gpu/drm/i915/intel_fbdev.c +0
-0@@ -366,12 +366,12 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,uint64_t conn_configured =0 , mask;
drivers/gpu/drm/i915/intel_fbdev.c static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper, · line 374
Quoted 10 lines
drivers/gpu/drm/i915/intel_fbdev.c +2
-2int pass =0 ; - save_enabled =kcalloc (dev->mode_config.num_connector,sizeof (bool ), + save_enabled =kcalloc (fb_helper->connector_count,sizeof (bool ),GFP_KERNEL );if (!save_enabled)return false; -memcpy (save_enabled, enabled, dev->mode_config.num_connector); +memcpy (save_enabled, enabled, fb_helper->connector_count);
If num_connector < connector_count this can still go boom. I think we need to create a local variable
int num_conn = min(..., ...);
and then use that all throughout. Plus a big comment that fbdev setup drops locks and hence might become inconsistent.
-Daniel
Quoted 19 lines
drivers/gpu/drm/i915/intel_fbdev.c +1
-1mask = (1 << fb_helper->connector_count) -1 ; retry:for (i =0 ; i < fb_helper->connector_count; i++) {@@ -510,7 +510,7 @@ retry:if (fallback) { bail:DRM_DEBUG_KMS ("Not using firmware configuration\n" ); -memcpy (enabled, save_enabled, dev->mode_config.num_connector); +memcpy (enabled, save_enabled, fb_helper->connector_count);kfree (save_enabled);return false; }Signature · 6 lines
2.5.5 _______________________________________________ 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