From: syzbot <syzbot+fe6eeea133f070606074@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de, daniel.vetter@ffwll.ch,
ggherdovich@suse.cz, gregkh@linuxfoundation.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, linux@dominikbrodowski.net,
mhiramat@kernel.org, mingo@redhat.com,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, peterz@infradead.org,
rafael.j.wysocki@intel.com, rkovhaev@gmail.com,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: Re: general protection fault in __switch_to_asm
Date: Mon, 19 Oct 2020 23:48:05 -0700 [thread overview]
Message-ID: <000000000000f3ad7805b2149c19@google.com> (raw)
In-Reply-To: <0000000000009dd95205a7b7f3bf@google.com>
syzbot suspects this issue was fixed by commit:
commit 033724d6864245a11f8e04c066002e6ad22b3fd0
Author: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Date: Wed Jul 15 01:51:02 2020 +0000
fbdev: Detect integer underflow at "struct fbcon_ops"->clear_margins.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17f3766f900000
start commit: 04300d66 Merge tag 'riscv-for-linus-5.8-rc7' of git://git...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f87a5e4232fdb267
dashboard link: https://syzkaller.appspot.com/bug?extid=fe6eeea133f070606074
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1575d102900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15dd6ac0900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fbdev: Detect integer underflow at "struct fbcon_ops"->clear_margins.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-10-20 6:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 10:03 general protection fault in __switch_to_asm syzbot
2020-10-20 6:48 ` syzbot [this message]
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=000000000000f3ad7805b2149c19@google.com \
--to=syzbot+fe6eeea133f070606074@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=daniel.vetter@ffwll.ch \
--cc=ggherdovich@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rkovhaev@gmail.com \
--cc=rostedt@goodmis.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