From: syzbot <syzbot+45862e7027be5d590577@syzkaller.appspotmail.com>
To: acme@kernel.org, alexander.shishkin@linux.intel.com,
bp@alien8.de, daniel.vetter@ffwll.ch, gregkh@linuxfoundation.org,
hpa@zytor.com, jolsa@redhat.com, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, mingo@redhat.com, namhyung@kernel.org,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, peterz@infradead.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: KASAN: out-of-bounds Read in pebs_update_state
Date: Sat, 15 Aug 2020 13:03:05 -0700 [thread overview]
Message-ID: <0000000000008eef2f05acf006f8@google.com> (raw)
In-Reply-To: <00000000000077346605a5a70a32@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=12ed4181900000
start commit: e99332e7 gcc-10: mark more functions __init to avoid secti..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8a96cf498e199d8b
dashboard link: https://syzkaller.appspot.com/bug?extid=45862e7027be5d590577
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17bb1714100000
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-08-15 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 3:02 KASAN: out-of-bounds Read in pebs_update_state syzbot
2020-08-15 20:03 ` 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=0000000000008eef2f05acf006f8@google.com \
--to=syzbot+45862e7027be5d590577@syzkaller.appspotmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=daniel.vetter@ffwll.ch \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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