From: Johannes Berg <johannes@sipsolutions.net>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: kmemleak - percpu reliability?
Date: Wed, 27 Apr 2016 11:00:34 +0200 [thread overview]
Message-ID: <1461747634.3723.4.camel@sipsolutions.net> (raw)
Hi,
Yesterday I found the bug fixed by this commit:
https://git.kernel.org/cgit/linux/kernel/git/jberg/mac80211.git/commit/?id=e6436be21e77e3659b4ff7e357ab5a8342d132d2
The first case can easily be reproduced by running:
# iw wlan0 interface add wlan0 type monitor
(reusing the name "wlan0" twice, the command should fail)
I tried to see what happens with kmemleak, but for some reason it won't
report it even with forced rescan etc.
Am I missing something?
Thanks,
johannes
next reply other threads:[~2016-04-27 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 9:00 Johannes Berg [this message]
2016-04-27 9:38 ` kmemleak - percpu reliability? Catalin Marinas
2016-04-27 9:40 ` Johannes Berg
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=1461747634.3723.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@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