From: oneukum@suse•com (Oliver Neukum)
To: linux-arm-kernel@lists•infradead.org
Subject: Kernel memory leak on CDC-ACM device plug/unplug
Date: Fri, 21 Sep 2018 10:08:24 +0200 [thread overview]
Message-ID: <1537517304.15252.0.camel@suse.com> (raw)
In-Reply-To: <CAGkQfmP6o+e_nanviTfRt7Ej9U+4BdqDYvMM83FjHhSCECcH3w@mail.gmail.com>
On Mi, 2018-09-19 at 16:11 +0200, Romain Izard wrote:
> While trying to debug a memory leak problem, I encountered the following
> problem:
>
> After plugging/unplugging an USB CDC-ACM device, kmemleak reports multiple
> copies of the following leak. It is not necessary to open the port for the
> leak to happen.
Hi,
nothing is immediately obvious to me. Could you compile a kernel with
CONFIG_DEBUG_KMEMLEAK?
Regards
Oliver
next prev parent reply other threads:[~2018-09-21 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 14:11 Kernel memory leak on CDC-ACM device plug/unplug Romain Izard
2018-09-19 20:32 ` Greg KH
2018-09-20 14:17 ` Romain Izard
2018-09-21 8:08 ` Oliver Neukum [this message]
2018-09-21 10:11 ` Romain Izard
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=1537517304.15252.0.camel@suse.com \
--to=oneukum@suse$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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