From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: pantelis.antoniou@konsulko.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
"Erhard F." <erhard_f@mailbox.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Alan Tull <atull@kernel.org>
Subject: Re: [PATCH 0/5] of: unittest: kmleak detected memory leaks
Date: Thu, 16 Apr 2020 17:10:06 -0500 [thread overview]
Message-ID: <20200416221006.GA3834@bogus> (raw)
In-Reply-To: <1587073370-25963-1-git-send-email-frowand.list@gmail.com>
On Thu, Apr 16, 2020 at 04:42:45PM -0500, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Original bug report:
> https://bugzilla.kernel.org/show_bug.cgi?id=206203
> https://lore.kernel.org/r/877dyqlles.fsf@mpe.ellerman.id.au
>
> kmemleak detected many memory leaks originating if devicetree
> unittests.
>
> Five separate causes were found. Four causes were bugs and
> one was expected.
>
> Fix the four bugs and modify the test that led to the expected
> memory leak to no longer have a memory leak.
>
>
> Frank Rowand (5):
> of: unittest: kmemleak on changeset destroy
> of: unittest: kmemleak in of_unittest_platform_populate()
> of: unittest: kmemleak in of_unittest_overlay_high_level()
> of: overlay: kmemleak in dup_and_fixup_symbol_prop()
> of: unittest: kmemleak in duplicate property update
Series applied. (To get into today's -next and I plan to send to Linus
tomorrow.)
Rob
prev parent reply other threads:[~2020-04-16 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 21:42 [PATCH 0/5] of: unittest: kmleak detected memory leaks frowand.list
2020-04-16 21:42 ` [PATCH 1/5] of: unittest: kmemleak on changeset destroy frowand.list
2020-04-16 21:42 ` [PATCH 2/5] of: unittest: kmemleak in of_unittest_platform_populate() frowand.list
2020-04-16 21:42 ` [PATCH 3/5] of: unittest: kmemleak in of_unittest_overlay_high_level() frowand.list
2020-04-16 21:42 ` [PATCH 4/5] of: overlay: kmemleak in dup_and_fixup_symbol_prop() frowand.list
2020-04-16 21:42 ` [PATCH 5/5] of: unittest: kmemleak in duplicate property update frowand.list
2020-04-16 22:11 ` Rob Herring
2020-04-16 22:10 ` Rob Herring [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=20200416221006.GA3834@bogus \
--to=robh@kernel.org \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=erhard_f@mailbox.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=pantelis.antoniou@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.