From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
"Murthy, Arun R" <arun.r.murthy@intel.com>,
"Deak, Imre" <imre.deak@intel.com>
Subject: RE: [PATCH] drm/display/dp_mst: Add protection against 0 vcpi
Date: Thu, 13 Nov 2025 12:26:53 +0200 [thread overview]
Message-ID: <b2b7c5cbec76955ffdcc0a7ebf6cd83ad67e8b04@intel.com> (raw)
In-Reply-To: <DM3PPF208195D8D7C8C263E115ABED5A500E3CDA@DM3PPF208195D8D.namprd11.prod.outlook.com>
On Thu, 13 Nov 2025, "Kandpal, Suraj" <suraj.kandpal@intel.com> wrote:
> .deak@intel.com>; Kandpal,
>> Suraj <suraj.kandpal@intel.com>
>> Subject: Re: [PATCH] drm/display/dp_mst: Add protection against 0 vcpi
>>
>> On Thu, 13 Nov 2025, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
>> > When releasing a timeslot there is a slight chance we may end up with
>> > the wrong payload mask due to overflow if the delayed_destroy_work
>> > ends up coming into play after a DP 2.1 monitor gets disconnected
>> > which causes vcpi to become 0 then we try to make the payload =
>> > ~BIT(vcpi - 1) which is a negative shift.
>>
>> Is that a real scenario or a hypothetical one?
>>
>
> This is a real scenario which ends up throwing the below error
> <7> [515.287237] xe 0000:03:00.0: [drm:drm_dp_mst_get_port_malloc [drm_display_helper]] port ffff888126ce9000 (3)
> <4> [515.287267] -----------[ cut here ]-----------
> <3> [515.287268] UBSAN: shift-out-of-bounds in ../drivers/gpu/drm/display/drm_dp_mst_topology.c:4575:36
> <3> [515.287271] shift exponent -1 is negative
> <4> [515.287275] CPU: 7 UID: 0 PID: 3108 Comm: kworker/u64:33 Tainted: G S U 6.17.0-rc6-lgci-xe-xe-3795-3e79699fa1b216e92+ #1 PREEMPT(voluntary)
> <4> [515.287279] Tainted: [S]=CPU_OUT_OF_SPEC, [U]=USER
> <4> [515.287279] Hardware name: ASUS System Product Name/PRIME Z790-P WIFI, BIOS 1645 03/15/2024
> <4> [515.287281] Workqueue: drm_dp_mst_wq drm_dp_delayed_destroy_work [drm_display_helper]
> <4> [515.287303] Call Trace:
> <4> [515.287304] <TASK>
> <4> [515.287306] dump_stack_lvl+0xc1/0xf0
> <4> [515.287313] dump_stack+0x10/0x20
> <4> [515.287316] __ubsan_handle_shift_out_of_bounds+0x133/0x2e0
> <4> [515.287324] ? drm_atomic_get_private_obj_state+0x186/0x1d0
> <4> [515.287333] drm_dp_atomic_release_time_slots.cold+0x17/0x3d [drm_display_helper]
> <4> [515.287355] mst_connector_atomic_check+0x159/0x180 [xe]
> <4> [515.287546] drm_atomic_helper_check_modeset+0x4d9/0xfa0
> <4> [515.287550] ? __ww_mutex_lock.constprop.0+0x6f/0x1a60
> <4> [515.287562] intel_atomic_check+0x119/0x2b80 [xe]
> <4> [515.287740] ? find_held_lock+0x31/0x90
> <4> [515.287747] ? lock_release+0xce/0x2a0
> <4> [515.287754] drm_atomic_check_only+0x6a2/0xb40
> <4> [515.287758] ? drm_atomic_add_affected_connectors+0x12b/0x140
> <4> [515.287765] drm_atomic_commit+0x6e/0xf0
> <4> [515.287766] ? _pfx__drm_printfn_info+0x10/0x10
> <4> [515.287774] drm_client_modeset_commit_atomic+0x25c/0x2b0
> <4> [515.287794] drm_client_modeset_commit_locked+0x60/0x1b0
> <4> [515.287795] ? mutex_lock_nested+0x1b/0x30
> <4> [515.287801] drm_client_modeset_commit+0x26/0x50
> <4> [515.287804] __drm_fb_helper_restore_fbdev_mode_unlocked+0xdc/0x110
> <4> [515.287810] drm_fb_helper_hotplug_event+0x120/0x140
> <4> [515.287814] drm_fbdev_client_hotplug+0x28/0xd0
> <4> [515.287819] drm_client_hotplug+0x6c/0xf0
> <4> [515.287824] drm_client_dev_hotplug+0x9e/0xd0
> <4> [515.287829] drm_kms_helper_hotplug_event+0x1a/0x30
> <4> [515.287834] drm_dp_delayed_destroy_work+0x3df/0x410 [drm_display_helper]
> <4> [515.287861] process_one_work+0x22b/0x6f0
> <4> [515.287874] worker_thread+0x1e8/0x3d0
> <4> [515.287879] ? __pfx_worker_thread+0x10/0x10
> <4> [515.287882] kthread+0x11c/0x250
> <4> [515.287886] ? __pfx_kthread+0x10/0x10
> <4> [515.287890] ret_from_fork+0x2d7/0x310
> <4> [515.287894] ? __pfx_kthread+0x10/0x10
> <4> [515.287897] ret_from_fork_asm+0x1a/0x30
>
> Refer to gitlab xe issue: 6303
Both the backtrace and the gitlab reference should be part of the commit
message...
>
> Regards,
> Suraj Kandpal
>
>> >
>> > Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> > ---
>> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 4 +++-
>> > 1 file changed, 3 insertions(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > index 64e5c176d5cc..3cf1eafcfcb5 100644
>> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > @@ -4531,6 +4531,7 @@ int drm_dp_atomic_release_time_slots(struct
>> drm_atomic_state *state,
>> > struct drm_dp_mst_atomic_payload *payload;
>> > struct drm_connector_state *old_conn_state, *new_conn_state;
>> > bool update_payload = true;
>> > + int bit;
>> >
>> > old_conn_state = drm_atomic_get_old_connector_state(state, port-
>> >connector);
>> > if (!old_conn_state->crtc)
>> > @@ -4572,7 +4573,8 @@ int drm_dp_atomic_release_time_slots(struct
>> drm_atomic_state *state,
>> > if (!payload->delete) {
>> > payload->pbn = 0;
>> > payload->delete = true;
>> > - topology_state->payload_mask &= ~BIT(payload->vcpi - 1);
>> > + bit = payload->vcpi ? payload->vcpi - 1 : 0;
>> > + topology_state->payload_mask &= ~BIT(bit);
>> > }
>> >
>> > return 0;
>>
>> --
>> Jani Nikula, Intel
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-11-13 10:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 4:39 [PATCH] drm/display/dp_mst: Add protection against 0 vcpi Suraj Kandpal
2025-11-13 4:46 ` ✓ CI.KUnit: success for " Patchwork
2025-11-13 5:37 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-13 8:21 ` [PATCH] " Imre Deak
2025-11-13 16:24 ` Jani Nikula
2025-11-17 5:09 ` Kandpal, Suraj
2025-11-17 10:08 ` Imre Deak
2025-11-17 10:19 ` Jani Nikula
2025-11-17 10:41 ` Imre Deak
2025-11-19 7:38 ` Kandpal, Suraj
2025-11-19 9:15 ` Imre Deak
2025-11-19 9:26 ` Kandpal, Suraj
2025-11-13 8:25 ` Jani Nikula
2025-11-13 8:54 ` Kandpal, Suraj
2025-11-13 10:26 ` Jani Nikula [this message]
2025-11-13 16:10 ` Jani Nikula
2025-11-13 12:30 ` ✓ Xe.CI.Full: success for " Patchwork
2025-11-19 9:46 ` [PATCH v2] " Suraj Kandpal
2025-11-21 17:33 ` Imre Deak
2025-11-26 23:11 ` Lyude Paul
2025-11-19 10:11 ` ✗ CI.checkpatch: warning for drm/display/dp_mst: Add protection against 0 vcpi (rev2) Patchwork
2025-11-19 10:12 ` ✓ CI.KUnit: success " Patchwork
2025-11-19 10:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-19 13:39 ` ✗ Xe.CI.Full: failure " Patchwork
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=b2b7c5cbec76955ffdcc0a7ebf6cd83ad67e8b04@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
/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