From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: krzk@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] pinctrl: samsung: Fix device node refcount leaks in S3C64xx" failed to apply to 4.9-stable tree
Date: Sun, 15 Dec 2019 14:11:45 -0500 [thread overview]
Message-ID: <20191215191145.GS18043@sasha-vm> (raw)
In-Reply-To: <1576416657206164@kroah.com>
On Sun, Dec 15, 2019 at 02:30:57PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.9-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>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 7f028caadf6c37580d0f59c6c094ed09afc04062 Mon Sep 17 00:00:00 2001
>From: Krzysztof Kozlowski <krzk@kernel.org>
>Date: Mon, 5 Aug 2019 18:27:09 +0200
>Subject: [PATCH] pinctrl: samsung: Fix device node refcount leaks in S3C64xx
> wakeup controller init
>
>In s3c64xx_eint_eint0_init() the for_each_child_of_node() loop is used
>with a break to find a matching child node. Although each iteration of
>for_each_child_of_node puts the previous node, but early exit from loop
>misses it. This leads to leak of device node.
>
>Cc: <stable@vger.kernel.org>
>Fixes: 61dd72613177 ("pinctrl: Add pinctrl-s3c64xx driver")
>Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
Fixed up context and queued for 4.9 and 4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2019-12-15 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 13:30 FAILED: patch "[PATCH] pinctrl: samsung: Fix device node refcount leaks in S3C64xx" failed to apply to 4.9-stable tree gregkh
2019-12-15 19:11 ` Sasha Levin [this message]
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=20191215191145.GS18043@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@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