From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>
Cc: Ingo Molnar <mingo@kernel.org>, Andy Lutomirski <luto@kernel.org>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Mateusz Guzik <mguzik@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: kmemleak splat on copy_process()
Date: Fri, 3 Feb 2017 13:06:04 -0800 [thread overview]
Message-ID: <CAB=NE6VZXq3y-3pfouYTBUco2Cq2xqoLZrgDFdVx+_=_=SwG_Q@mail.gmail.com> (raw)
On next-20170125 running some kselftest not yet upstream I eventually
get a kmemleak splat:
unreferenced object 0xffffa7b1034b4000 (size 16384):
comm "driver_data.sh", pid 6506, jiffies 4295068366 (age 1697.272s)
hex dump (first 32 bytes):
9d 6e ac 57 00 00 00 00 74 2d 64 72 69 76 65 72 .n.W....t-driver
5f 64 61 74 61 2e 62 69 6e 0a 00 00 00 00 00 00 _data.bin.......
backtrace:
[<ffffffff9005f7fa>] kmemleak_alloc+0x4a/0xa0
[<ffffffff8fbe7006>] __vmalloc_node_range+0x206/0x2a0
[<ffffffff8fa7f3e9>] copy_process.part.36+0x609/0x1cc0
[<ffffffff8fa80c77>] _do_fork+0xd7/0x390
[<ffffffff8fa80fd9>] SyS_clone+0x19/0x20
[<ffffffff8fa03b4b>] do_syscall_64+0x5b/0xc0
[<ffffffff9006b3af>] return_from_SYSCALL_64+0x0/0x6a
[<ffffffffffffffff>] 0xffffffffffffffff
As per gdb:
(gdb) l *(copy_process+0x609)
0xffffffff8107f3e9 is in copy_process (kernel/fork.c:204).
warning: Source file is more recent than executable.
199 /*
200 * We can't call find_vm_area() in interrupt context, and
201 * free_thread_stack() can be called in interrupt context,
202 * so cache the vm_struct.
203 */
204 if (stack) {
205 tsk->stack_vm_area = find_vm_area(stack);
206 }
207 return stack;
208 #else
So it would seem a complaint about alloc_thread_stack_node() -- I
checked but I cannot find the leak so am thinking this is a false
positive. Can you confirm?
Luis
next reply other threads:[~2017-02-03 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 21:06 Luis R. Rodriguez [this message]
2017-02-06 9:47 ` kmemleak splat on copy_process() Michal Hocko
2017-02-07 1:37 ` Luis R. Rodriguez
2017-02-07 8:03 ` Michal Hocko
2017-02-09 1:37 ` Luis R. Rodriguez
2017-02-17 17:07 ` Andy Lutomirski
2017-02-17 17:23 ` Luis R. Rodriguez
2017-02-17 19:32 ` Andy Lutomirski
2017-05-15 21:53 ` Luis R. Rodriguez
2017-05-16 6:28 ` Michal Hocko
2017-05-16 13:39 ` Catalin Marinas
2017-05-16 23:55 ` Andy Lutomirski
2017-05-17 11:09 ` Catalin Marinas
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='CAB=NE6VZXq3y-3pfouYTBUco2Cq2xqoLZrgDFdVx+_=_=SwG_Q@mail.gmail.com' \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mguzik@redhat.com \
--cc=mhocko@suse.com \
--cc=mingo@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 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.