From: Catalin Marinas <catalin.marinas@arm.com>
To: syzbot <syzbot+a871c1e6ea00685e73d7@syzkaller.appspotmail.com>
Cc: alexandre.belloni@free-electrons.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
nicolas.ferre@atmel.com, robh@kernel.org, sre@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: memory leak in vq_meta_prefetch
Date: Fri, 26 Jul 2019 14:00:14 +0100 [thread overview]
Message-ID: <20190726130013.GC2368@arrakis.emea.arm.com> (raw)
In-Reply-To: <00000000000052ad6b058e722ba4@google.com>
On Wed, Jul 24, 2019 at 12:18:07PM -0700, syzbot wrote:
> syzbot found the following crash on:
>
> HEAD commit: c6dd78fc Merge branch 'x86-urgent-for-linus' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15fffef4600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=8de7d700ea5ac607
> dashboard link: https://syzkaller.appspot.com/bug?extid=a871c1e6ea00685e73d7
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127b0334600000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12609e94600000
>
> The bug was bisected to:
>
> commit 0e5f7d0b39e1f184dc25e3adb580c79e85332167
> Author: Nicolas Ferre <nicolas.ferre@atmel.com>
> Date: Wed Mar 16 13:19:49 2016 +0000
>
> ARM: dts: at91: shdwc binding: add new shutdown controller documentation
That's another wrong commit identification (a documentation patch should
not cause a memory leak).
I don't really think kmemleak, with its relatively high rate of false
positives, is suitable for automated testing like syzbot. You could
reduce the false positives if you add support for scanning in
stop_machine(). Otherwise, in order to avoid locking the kernel for long
periods, kmemleak runs concurrently with other threads (even on the
current CPU) and under high load, pointers are missed (e.g. they are in
CPU registers rather than stack).
--
Catalin
next prev parent reply other threads:[~2019-07-26 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 19:18 syzbot
2019-07-26 13:00 ` Catalin Marinas [this message]
2019-07-26 15:20 ` Dmitry Vyukov
2019-07-26 15:57 ` Catalin Marinas
2019-07-26 16:05 ` Dmitry Vyukov
2019-07-26 16:15 ` Catalin Marinas
2019-07-26 16:26 ` Dmitry Vyukov
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=20190726130013.GC2368@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nicolas.ferre@atmel.com \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=syzbot+a871c1e6ea00685e73d7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox