diff options
| author |   Imre Deak <imre.deak@intel.com> | 2021-10-18 12:41:51 +0300 |
|---|---|---|
| committer |   Rodrigo Vivi <rodrigo.vivi@intel.com> | 2021-10-27 06:09:58 -0400 |
| commit | cc99bc62ff6902688ee7bd3a7b25eefc620fbb6a (patch) | |
| tree | 3bae32fd83f61cc15a1f7f420003ddd33d846dd8 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | drm/i915/dp: Ensure sink rate values are always valid (diff) | |
| download | linux-dev-cc99bc62ff6902688ee7bd3a7b25eefc620fbb6a.tar.xz linux-dev-cc99bc62ff6902688ee7bd3a7b25eefc620fbb6a.zip | |
drm/i915/dp: Ensure max link params are always valid
Atm until the DPCD for a connector is read the max link rate and lane
count params are invalid. If the connector is modeset, in
intel_dp_compute_config(), intel_dp_common_len_rate_limit(max_link_rate)
will return 0, leading to a intel_dp->common_rates[-1] access.
Fix the above by making sure the max link params are always valid.
The above access leads to an undefined behaviour by definition, though
not causing a user visible problem to my best knowledge, see the previous
patch why. Nevertheless it is an undefined behaviour and it triggers a
BUG() in CONFIG_UBSAN builds, hence CC:stable.
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Acked-by: Jani Nikula <jani.nikula@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20211018094154.1407705-4-imre.deak@intel.com
(cherry picked from commit 9ad87de4735620ffc555592e8c5f580478fa3ed0)
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions