diff options
author | Lyude <cpaul@redhat.com> | 2016-05-12 10:56:59 -0400 |
---|---|---|
committer | Sasha Levin <sasha.levin@oracle.com> | 2016-06-06 19:12:24 -0400 |
commit | 9a2257ff4ccf1ccd1ed0446f9ff5813232594ffc (patch) | |
tree | a30d4cb7eff2208a2fde6bb162ccadc872538119 /mm | |
parent | d648fcdb0adc44bafa01dc1cd0fbc3e4c9375488 (diff) | |
download | lwn-9a2257ff4ccf1ccd1ed0446f9ff5813232594ffc.tar.gz lwn-9a2257ff4ccf1ccd1ed0446f9ff5813232594ffc.zip |
drm/fb_helper: Fix references to dev->mode_config.num_connector
[ Upstream commit 255f0e7c418ad95a4baeda017ae6182ba9b3c423 ]
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.
Note: This is just polish for 4.7, Dave Airlie's drm_connector
refcounting fixed these bugs for real. But it's good enough duct-tape
for stable kernel backporting, since backporting the refcounting
changes is way too invasive.
Cc: stable@vger.kernel.org
Signed-off-by: Lyude <cpaul@redhat.com>
[danvet: Clarify why we need this. Also remove the now unused "dev"
local variable to appease gcc.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: http://patchwork.freedesktop.org/patch/msgid/1463065021-18280-3-git-send-email-cpaul@redhat.com
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions