linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [Bug 206203] kmemleak reports various leaks in drivers/of/unittest.c
Date: Thu, 16 Apr 2020 16:52:25 -0500	[thread overview]
Message-ID: <8ff9a2e5-9b49-73d3-6f57-2c5a62bc4f97@gmail.com> (raw)
In-Reply-To: <a717b335-de6c-46eb-1daa-ae5054664e93@gmail.com>

On 4/15/20 10:27 PM, Frank Rowand wrote:
> On 4/8/20 10:22 AM, Frank Rowand wrote:
>> Hi Michael,
>>
>> On 4/7/20 10:13 PM, Michael Ellerman wrote:
>>> bugzilla-daemon@bugzilla.kernel.org writes:
>>>> https://bugzilla.kernel.org/show_bug.cgi?id=206203
>>>>
>>>> Erhard F. (erhard_f@mailbox.org) changed:
>>>>
>>>>            What    |Removed                     |Added
>>>> ----------------------------------------------------------------------------
>>>>  Attachment #286801|0                           |1
>>>>         is obsolete|                            |
>>>>
>>>> --- Comment #10 from Erhard F. (erhard_f@mailbox.org) ---
>>>> Created attachment 288189
>>>>   --> https://bugzilla.kernel.org/attachment.cgi?id=288189&action=edit
>>>> kmemleak output (kernel 5.6.2, Talos II)
>>>
>>> These are all in or triggered by the of unittest code AFAICS.
>>> Content of the log reproduced below.
>>>
>>> Frank/Rob, are these memory leaks expected?
>>
>> Thanks for the report.  I'll look at each one.
> 
> Only one of the leaks was expected.  I have patches to fix the
> unexpected leaks and to remove the expected leak so that the
> kmemleak report of it will not have to be checked again.
> 
> I expect to send the patch series tomorrow (Thursday).

The patches for the memory leaks that I saw on an ARM board are at:

   https://lore.kernel.org/r/1587073370-25963-1-git-send-email-frowand.list@gmail.com

-Frank

< snip >

  reply	other threads:[~2020-04-16 21:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 15:51 [Bug 206203] New: kmemleak reports various leaks in drivers/of/unittest.c bugzilla-daemon
2020-01-14 15:54 ` [Bug 206203] " bugzilla-daemon
2020-01-14 15:55 ` bugzilla-daemon
2020-02-27 21:19 ` bugzilla-daemon
2020-02-27 22:06   ` Michael Ellerman
2020-02-27 21:20 ` bugzilla-daemon
2020-02-27 21:31 ` bugzilla-daemon
2020-02-27 22:07 ` bugzilla-daemon
2020-02-27 22:39 ` bugzilla-daemon
2020-04-03 19:22 ` bugzilla-daemon
2020-04-03 19:23 ` bugzilla-daemon
2020-04-03 19:23 ` bugzilla-daemon
2020-04-08  3:13   ` Michael Ellerman
2020-04-08 15:22     ` Frank Rowand
2020-04-16  3:27       ` Frank Rowand
2020-04-16 21:52         ` Frank Rowand [this message]
2020-04-17 15:46 ` bugzilla-daemon
2020-04-17 15:47 ` bugzilla-daemon
2020-06-15 20:43 ` bugzilla-daemon
2020-06-15 20:45 ` bugzilla-daemon
2020-06-15 20:53 ` bugzilla-daemon
2020-07-28  7:18 ` bugzilla-daemon
2020-07-28  7:19 ` bugzilla-daemon
2020-09-02 14:38 ` bugzilla-daemon
2020-09-02 14:39 ` bugzilla-daemon
2020-09-02 14:45 ` bugzilla-daemon
2021-03-03 20:57 ` bugzilla-daemon
2022-11-20 17:18 ` bugzilla-daemon
2022-11-20 17:24 ` bugzilla-daemon
2022-11-20 17:24 ` bugzilla-daemon
2022-11-20 17:25 ` bugzilla-daemon
2023-10-31 16:44 ` bugzilla-daemon

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=8ff9a2e5-9b49-73d3-6f57-2c5a62bc4f97@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=robh+dt@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).