public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: gregkh@linuxfoundation.org
Cc: johan@kernel.org, airlied@linux.ie, jcrouse@codeaurora.org,
	robdclark@gmail.com, robh@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/msm: fix OF child-node lookup" failed to apply to 4.14-stable tree
Date: Tue, 27 Nov 2018 07:19:38 -0800	[thread overview]
Message-ID: <20181127151938.GS2403@localhost> (raw)
In-Reply-To: <154263645736118@kroah.com>

On Mon, Nov 19, 2018 at 03:07:37PM +0100, Greg Kroah-Hartman wrote:
> 
> The patch below does not apply to the 4.14-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.

This one also depends on

	36156f9241cb ("of: add helper to lookup compatible child node")

Johan

> ------------------ original commit in Linus's tree ------------------
> 
> From f9a7082327e26f54067a49cac2316d31e0cc8ba7 Mon Sep 17 00:00:00 2001
> From: Johan Hovold <johan@kernel.org>
> Date: Mon, 27 Aug 2018 10:21:47 +0200
> Subject: [PATCH] drm/msm: fix OF child-node lookup
> 
> Use the new of_get_compatible_child() helper to lookup the legacy
> pwrlevels child node instead of using of_find_compatible_node(), which
> searches the entire tree from a given start node and thus can return an
> unrelated (i.e.  non-child) node.
> 
> This also addresses a potential use-after-free (e.g. after probe
> deferral) as the tree-wide helper drops a reference to its first
> argument (i.e. the probed device's node).
> 
> While at it, also fix the related child-node reference leak.
> 
> Fixes: e2af8b6b0ca1 ("drm/msm: gpu: Use OPP tables if we can")
> Cc: stable <stable@vger.kernel.org>     # 4.12
> Cc: Jordan Crouse <jcrouse@codeaurora.org>
> Cc: Rob Clark <robdclark@gmail.com>
> Cc: David Airlie <airlied@linux.ie>
> Signed-off-by: Johan Hovold <johan@kernel.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> 
> diff --git a/drivers/gpu/drm/msm/adreno/adreno_gpu.c b/drivers/gpu/drm/msm/adreno/adreno_gpu.c
> index da1363a0c54d..93d70f4a2154 100644
> --- a/drivers/gpu/drm/msm/adreno/adreno_gpu.c
> +++ b/drivers/gpu/drm/msm/adreno/adreno_gpu.c
> @@ -633,8 +633,7 @@ static int adreno_get_legacy_pwrlevels(struct device *dev)
>  	struct device_node *child, *node;
>  	int ret;
>  
> -	node = of_find_compatible_node(dev->of_node, NULL,
> -		"qcom,gpu-pwrlevels");
> +	node = of_get_compatible_child(dev->of_node, "qcom,gpu-pwrlevels");
>  	if (!node) {
>  		dev_err(dev, "Could not find the GPU powerlevels\n");
>  		return -ENXIO;
> @@ -655,6 +654,8 @@ static int adreno_get_legacy_pwrlevels(struct device *dev)
>  			dev_pm_opp_add(dev, val, 0);
>  	}
>  
> +	of_node_put(node);
> +
>  	return 0;
>  }
>  
> 

  reply	other threads:[~2018-11-28  2:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 14:07 FAILED: patch "[PATCH] drm/msm: fix OF child-node lookup" failed to apply to 4.14-stable tree gregkh
2018-11-27 15:19 ` Johan Hovold [this message]
2018-11-29  8:06   ` Greg KH
2018-12-05  7:38     ` Johan Hovold
2018-12-06 10:40       ` Greg KH

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=20181127151938.GS2403@localhost \
    --to=johan@kernel.org \
    --cc=airlied@linux.ie \
    --cc=gregkh@linuxfoundation.org \
    --cc=jcrouse@codeaurora.org \
    --cc=robdclark@gmail.com \
    --cc=robh@kernel.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