From: syzbot <syzbot+2667188e965125ab6e7a@syzkaller.appspotmail.com>
To: 0x7f454c46@gmail.com, anant.thazhemadam@gmail.com,
b.zolnierkie@samsung.com, bp@alien8.de, chang.seok.bae@intel.com,
dan.carpenter@oracle.com, george.kennedy@oracle.com,
hpa@zytor.com, linux-kernel@vger.kernel.org, luto@kernel.org,
mingo@redhat.com, sashal@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: KASAN: out-of-bounds Read in __switch_to (2)
Date: Thu, 29 Oct 2020 07:10:08 -0700 [thread overview]
Message-ID: <00000000000068a67705b2cfd6e9@google.com> (raw)
In-Reply-To: <000000000000a4b3c205b0c24743@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=174684b8500000
start commit: fb0155a0 Merge tag 'nfs-for-5.9-3' of git://git.linux-nfs...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=41b736b7ce1b3ea4
dashboard link: https://syzkaller.appspot.com/bug?extid=2667188e965125ab6e7a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11743a37900000
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-10-29 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 11:09 KASAN: out-of-bounds Read in __switch_to (2) syzbot
2020-10-29 14:10 ` syzbot [this message]
2020-11-11 11:09 ` 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=00000000000068a67705b2cfd6e9@google.com \
--to=syzbot+2667188e965125ab6e7a@syzkaller.appspotmail.com \
--cc=0x7f454c46@gmail.com \
--cc=anant.thazhemadam@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--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=sashal@kernel.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.