From: syzbot <syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luto@kernel.org, mingo@kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: kernel BUG at mm/vmalloc.c:LINE! (2)
Date: Tue, 21 Jul 2020 23:17:04 -0700 [thread overview]
Message-ID: <00000000000043f09405ab01b0b8@google.com> (raw)
In-Reply-To: <000000000000588c2c05aa156b2b@google.com>
syzbot has bisected this issue to:
commit bdbfb1d52d5e576c1d275fd8ab59b677011229e8
Author: Ingo Molnar <mingo@kernel.org>
Date: Sun Jun 7 19:12:51 2020 +0000
Revert "mm/vmalloc: modify struct vmap_area to reduce its size"
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=166e6b7f100000
start commit: ab8be66e Add linux-next specific files for 20200720
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=156e6b7f100000
console output: https://syzkaller.appspot.com/x/log.txt?x=116e6b7f100000
kernel config: https://syzkaller.appspot.com/x/.config?x=c4bf77d63d0cf88c
dashboard link: https://syzkaller.appspot.com/bug?extid=5f326d255ca648131f87
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=151192bb100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d7a873100000
Reported-by: syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com
Fixes: bdbfb1d52d5e ("Revert "mm/vmalloc: modify struct vmap_area to reduce its size"")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-07-22 6:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:24 kernel BUG at mm/vmalloc.c:LINE! (2) syzbot
2020-07-20 16:48 ` syzbot
2020-07-20 16:48 ` syzbot
2020-07-20 20:06 ` Uladzislau Rezki
2020-07-22 14:28 ` Qian Cai
2020-07-22 14:46 ` Uladzislau Rezki
2020-07-24 2:50 ` Andrew Morton
2020-07-24 3:11 ` Stephen Rothwell
2020-07-24 4:28 ` Stephen Rothwell
2020-07-24 7:47 ` Thomas Gleixner
2020-07-22 6:17 ` syzbot [this message]
2020-07-22 6:17 ` syzbot
2021-01-10 21:34 ` syzbot
2021-01-10 21:34 ` syzbot
2021-01-11 9:15 ` Dmitry Vyukov
2022-01-24 17:59 ` Vegard Nossum
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=00000000000043f09405ab01b0b8@google.com \
--to=syzbot+5f326d255ca648131f87@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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.