Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, Lyude Paul <lyude@redhat.com>,
	stable@vger.kernel.org
Subject: [PATCH 2/7] drm/dp_mst: Verify request type in the corresponding down message reply
Date: Tue,  3 Dec 2024 18:02:18 +0200	[thread overview]
Message-ID: <20241203160223.2926014-3-imre.deak@intel.com> (raw)
In-Reply-To: <20241203160223.2926014-1-imre.deak@intel.com>

After receiving the response for an MST down request message, the
response should be accepted/parsed only if the response type matches
that of the request. Ensure this by checking if the request type code
stored both in the request and the reply match, dropping the reply in
case of a mismatch.

This fixes the topology detection for an MST hub, as described in the
Closes link below, where the hub sends an incorrect reply message after
a CLEAR_PAYLOAD_TABLE -> LINK_ADDRESS down request message sequence.

Cc: Lyude Paul <lyude@redhat.com>
Cc: <stable@vger.kernel.org>
Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12804
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
 drivers/gpu/drm/display/drm_dp_mst_topology.c | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)

diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
index 1475aa95ab6b2..bcf3a33123be1 100644
--- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
@@ -3941,6 +3941,34 @@ drm_dp_get_one_sb_msg(struct drm_dp_mst_topology_mgr *mgr, bool up,
 	return true;
 }
 
+static int get_msg_request_type(u8 data)
+{
+	return data & 0x7f;
+}
+
+static bool verify_rx_request_type(struct drm_dp_mst_topology_mgr *mgr,
+				   const struct drm_dp_sideband_msg_tx *txmsg,
+				   const struct drm_dp_sideband_msg_rx *rxmsg)
+{
+	const struct drm_dp_sideband_msg_hdr *hdr = &rxmsg->initial_hdr;
+	const struct drm_dp_mst_branch *mstb = txmsg->dst;
+	int tx_req_type = get_msg_request_type(txmsg->msg[0]);
+	int rx_req_type = get_msg_request_type(rxmsg->msg[0]);
+	char rad_str[64];
+
+	if (tx_req_type == rx_req_type)
+		return true;
+
+	drm_dp_mst_rad_to_str(mstb->rad, mstb->lct, rad_str, sizeof(rad_str));
+	drm_dbg_kms(mgr->dev,
+		    "Got unexpected MST reply, mstb: %p seqno: %d lct: %d rad: %s rx_req_type: %s (%02x) != tx_req_type: %s (%02x)\n",
+		    mstb, hdr->seqno, mstb->lct, rad_str,
+		    drm_dp_mst_req_type_str(rx_req_type), rx_req_type,
+		    drm_dp_mst_req_type_str(tx_req_type), tx_req_type);
+
+	return false;
+}
+
 static int drm_dp_mst_handle_down_rep(struct drm_dp_mst_topology_mgr *mgr)
 {
 	struct drm_dp_sideband_msg_tx *txmsg;
@@ -3970,6 +3998,9 @@ static int drm_dp_mst_handle_down_rep(struct drm_dp_mst_topology_mgr *mgr)
 		goto out_clear_reply;
 	}
 
+	if (!verify_rx_request_type(mgr, txmsg, msg))
+		goto out_clear_reply;
+
 	drm_dp_sideband_parse_reply(mgr, msg, &txmsg->reply);
 
 	if (txmsg->reply.reply_type == DP_SIDEBAND_REPLY_NAK) {
-- 
2.44.2


  parent reply	other threads:[~2024-12-03 16:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 16:02 [PATCH 0/7] drm/dp_mst: Fix a few side-band message handling issues Imre Deak
2024-12-03 16:02 ` [PATCH 1/7] drm/dp_mst: Fix resetting msg rx state after topology removal Imre Deak
2024-12-03 16:02 ` Imre Deak [this message]
2024-12-03 16:02 ` [PATCH 3/7] drm/dp_mst: Simplify error path in drm_dp_mst_handle_down_rep() Imre Deak
2024-12-03 16:02 ` [PATCH 4/7] drm/dp_mst: Fix down request message timeout handling Imre Deak
2024-12-03 17:46   ` [PATCH v2 " Imre Deak
2024-12-03 16:02 ` [PATCH 5/7] drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req() Imre Deak
2024-12-04 13:20   ` [PATCH v2 " Imre Deak
2024-12-03 16:02 ` [PATCH 6/7] drm/dp_mst: Reset message rx state after OOM " Imre Deak
2024-12-03 16:02 ` [PATCH 7/7] drm/dp_mst: Use reset_msg_rx_state() instead of open coding it Imre Deak
2024-12-03 16:34 ` ✗ Fi.CI.CHECKPATCH: warning for drm/dp_mst: Fix a few side-band message handling issues Patchwork
2024-12-03 16:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-12-03 16:50 ` ✗ i915.CI.BAT: failure " Patchwork
2024-12-03 17:07   ` Imre Deak
2024-12-04  6:09     ` Ravali, JupallyX
2024-12-03 18:03 ` [PATCH 0/7] " Lyude Paul
2024-12-03 18:28 ` ✗ Fi.CI.CHECKPATCH: warning for drm/dp_mst: Fix a few side-band message handling issues (rev2) Patchwork
2024-12-03 18:28 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-12-03 18:44 ` ✗ i915.CI.BAT: failure " Patchwork
2024-12-04  6:05 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-04  7:17 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-04 14:07 ` ✗ Fi.CI.CHECKPATCH: warning for drm/dp_mst: Fix a few side-band message handling issues (rev3) Patchwork
2024-12-04 14:07 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-12-04 14:22 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-04 15:30 ` ✓ i915.CI.Full: " Patchwork
2024-12-05 15:16   ` Imre Deak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241203160223.2926014-3-imre.deak@intel.com \
    --to=imre.deak@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox