From: Lyude Paul <cpaul@redhat.com>
To: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>,
dri-devel@lists.freedesktop.org
Cc: Alexander.Deucher@amd.com, Mykola.Lysenko@amd.com,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/dp/mst: Always clear proposed vcpi table for port.
Date: Tue, 24 May 2016 11:00:53 -0400 [thread overview]
Message-ID: <1464102053.18942.0.camel@redhat.com> (raw)
In-Reply-To: <1463714317-14392-1-git-send-email-Andrey.Grodzovsky@amd.com>
Looks good to me.
Reviewed-by: Lyude <cpaul@redhat.com>
On Thu, 2016-05-19 at 23:18 -0400, Andrey Grodzovsky wrote:
> Not clearing mst manager's proposed vcpis table for destroyed
> connectors when the manager is stopped leaves it pointing to
> unrefernced memory, this causes pagefault when the manager is
> restarted when plugging back a branch.
>
> Signed-off-by: Andrey Grodzovsky <Andrey.Grodzovsky@amd.com>
> ---
> drivers/gpu/drm/drm_dp_mst_topology.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
> b/drivers/gpu/drm/drm_dp_mst_topology.c
> index 9971c46..cd6014b 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -2881,11 +2881,9 @@ static void drm_dp_destroy_connector_work(struct
> work_struct *work)
> drm_dp_port_teardown_pdt(port, port->pdt);
>
> if (!port->input && port->vcpi.vcpi > 0) {
> - if (mgr->mst_state) {
> - drm_dp_mst_reset_vcpi_slots(mgr, port);
> - drm_dp_update_payload_part1(mgr);
> - drm_dp_mst_put_payload_id(mgr, port-
> >vcpi.vcpi);
> - }
> + drm_dp_mst_reset_vcpi_slots(mgr, port);
> + drm_dp_update_payload_part1(mgr);
> + drm_dp_mst_put_payload_id(mgr, port->vcpi.vcpi);
> }
>
> kref_put(&port->kref, drm_dp_free_mst_port);
next prev parent reply other threads:[~2016-05-24 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 3:18 [PATCH] drm/dp/mst: Always clear proposed vcpi table for port Andrey Grodzovsky
2016-05-23 8:38 ` Jani Nikula
2016-05-24 15:00 ` Lyude Paul [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-25 16:08 Andrey Grodzovsky
2016-05-25 18:19 ` Greg KH
2016-05-25 20:45 Andrey Grodzovsky
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=1464102053.18942.0.camel@redhat.com \
--to=cpaul@redhat.com \
--cc=Alexander.Deucher@amd.com \
--cc=Andrey.Grodzovsky@amd.com \
--cc=Mykola.Lysenko@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--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