From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: frank.rowand@sony.com, erhard_f@mailbox.org, robh@kernel.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] of: unittest: kmemleak in of_unittest_platform_populate()" failed to apply to 4.14-stable tree
Date: Tue, 21 Apr 2020 20:25:20 -0400 [thread overview]
Message-ID: <20200422002520.GP1809@sasha-vm> (raw)
In-Reply-To: <1587488977126108@kroah.com>
On Tue, Apr 21, 2020 at 07:09:37PM +0200, gregkh@linuxfoundation.org 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>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 216830d2413cc61be3f76bc02ffd905e47d2439e Mon Sep 17 00:00:00 2001
>From: Frank Rowand <frank.rowand@sony.com>
>Date: Thu, 16 Apr 2020 16:42:47 -0500
>Subject: [PATCH] of: unittest: kmemleak in of_unittest_platform_populate()
>
>kmemleak reports several memory leaks from devicetree unittest.
>This is the fix for problem 2 of 5.
>
>of_unittest_platform_populate() left an elevated reference count for
>grandchild nodes (which are platform devices). Fix the platform
>device reference counts so that the memory will be freed.
>
>Fixes: fb2caa50fbac ("of/selftest: add testcase for nodes with same name and address")
>Reported-by: Erhard F. <erhard_f@mailbox.org>
>Signed-off-by: Frank Rowand <frank.rowand@sony.com>
>Signed-off-by: Rob Herring <robh@kernel.org>
Conflict with a613b26a5013 ("of: Convert to using %pOFn instead of
device_node.name"). Fixed and queued for 4.14-4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-04-22 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 17:09 FAILED: patch "[PATCH] of: unittest: kmemleak in of_unittest_platform_populate()" failed to apply to 4.14-stable tree gregkh
2020-04-22 0:25 ` 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=20200422002520.GP1809@sasha-vm \
--to=sashal@kernel.org \
--cc=erhard_f@mailbox.org \
--cc=frank.rowand@sony.com \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).