From: syzbot <syzbot+d6459d8f8984c0929e54@syzkaller.appspotmail.com>
To: alexandre.chartre@oracle.com, b.zolnierkie@samsung.com,
bp@alien8.de, dan.carpenter@oracle.com,
george.kennedy@oracle.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: kernel panic: stack is corrupted in get_kernel_gp_address
Date: Fri, 13 Nov 2020 00:27:07 -0800 [thread overview]
Message-ID: <0000000000004c208d05b3f8cbb6@google.com> (raw)
In-Reply-To: <000000000000bb202905af132b8f@google.com>
syzbot suspects this issue was fixed by commit:
commit a49145acfb975d921464b84fe00279f99827d816
Author: George Kennedy <george.kennedy@oracle.com>
Date: Tue Jul 7 19:26:03 2020 +0000
fbmem: add margin check to fb_check_caps()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10ff7572500000
start commit: f4d51dff Linux 5.9-rc4
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
dashboard link: https://syzkaller.appspot.com/bug?extid=d6459d8f8984c0929e54
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=164270dd900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fbmem: add margin check to fb_check_caps()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-13 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 0:49 kernel panic: stack is corrupted in get_kernel_gp_address syzbot
2020-11-13 8:27 ` syzbot [this message]
2020-11-13 9:38 ` 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=0000000000004c208d05b3f8cbb6@google.com \
--to=syzbot+d6459d8f8984c0929e54@syzkaller.appspotmail.com \
--cc=alexandre.chartre@oracle.com \
--cc=b.zolnierkie@samsung.com \
--cc=bp@alien8.de \
--cc=dan.carpenter@oracle.com \
--cc=george.kennedy@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).