Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"Syrjala, Ville" <ville.syrjala@intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Peres, Martin" <martin.peres@intel.com>,
	"lyude@redhat.com" <lyude@redhat.com>
Subject: Re: [PATCH v2] drm: Check if primary mst is null
Date: Thu, 8 Nov 2018 09:18:35 +0000	[thread overview]
Message-ID: <770201ce72ec1dd36cc8a98d98ce766618882546.camel@intel.com> (raw)
In-Reply-To: <20181108082057.29001-1-stanislav.lisovskiy@intel.com>

On Thu, 2018-11-08 at 10:20 +0200, Stanislav Lisovskiy wrote:
> Unfortunately drm_dp_get_mst_branch_device which is called from both
> drm_dp_mst_handle_down_rep and drm_dp_mst_handle_up_rep seem to rely
> on that mgr->mst_primary is not NULL, which seem to be wrong as it
> can be
> cleared with simultaneous mode set, if probing fails or in other
> case.
> mgr->lock mutex doesn't protect against that as it might just get
> assigned to NULL right before, not simultaneously.
> 
> There are currently bugs 107738, 108616 bugs which crash in
> drm_dp_get_mst_branch_device, caused by this issue.
> 
> v2: Refactored the code, as it was nicely noticed.
>     Fixed Bugzilla bug numbers(second was 108616, but not 108816)
>     and added links.
> 

Hi Lyude Paul,

Thank you for quick review, just poking you
here as requested :)

> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108616
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107738
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>  drivers/gpu/drm/drm_dp_mst_topology.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
> b/drivers/gpu/drm/drm_dp_mst_topology.c
> index 5ff1d79b86c4..0e0df398222d 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -1275,6 +1275,9 @@ static struct drm_dp_mst_branch
> *drm_dp_get_mst_branch_device(struct drm_dp_mst_
>  	mutex_lock(&mgr->lock);
>  	mstb = mgr->mst_primary;
>  
> +	if (!mstb)
> +		goto out;
> +
>  	for (i = 0; i < lct - 1; i++) {
>  		int shift = (i % 2) ? 0 : 4;
>  		int port_num = (rad[i / 2] >> shift) & 0xf;
-- 
Best Regards,

Lisovskiy Stanislav

  reply	other threads:[~2018-11-08  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  8:20 [PATCH v2] drm: Check if primary mst is null Stanislav Lisovskiy
2018-11-08  9:18 ` Lisovskiy, Stanislav [this message]
2018-11-08  9:21 ` ✗ Fi.CI.BAT: failure for drm: Check if primary mst is null (rev2) Patchwork
2018-11-08  9:45   ` Lisovskiy, Stanislav
2018-11-09  8:25 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-09 13:46 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2018-11-09  9:00 [PATCH v2] drm: Check if primary mst is null Stanislav Lisovskiy
2018-11-09 17:29 ` Lyude Paul

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=770201ce72ec1dd36cc8a98d98ce766618882546.camel@intel.com \
    --to=stanislav.lisovskiy@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lyude@redhat.com \
    --cc=martin.peres@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=ville.syrjala@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