From: syzbot <syzbot+d9ae84069cff753e94bf@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, aryabinin@virtuozzo.com,
b.zolnierkie@samsung.com, christian@brauner.io,
dan.carpenter@oracle.com, dvyukov@google.com,
ebiederm@xmission.com, george.kennedy@oracle.com,
glider@google.com, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org, mingo@kernel.org,
peterz@infradead.org, sandeen@sandeen.net,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: KASAN: unknown-crash Read in do_exit
Date: Mon, 19 Oct 2020 14:38:04 -0700 [thread overview]
Message-ID: <000000000000f098f005b20ced50@google.com> (raw)
In-Reply-To: <00000000000005f0b605af42ab4e@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=17ce19c8500000
start commit: 729e3d09 Merge tag 'ceph-for-5.9-rc5' of git://github.com/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=c61610091f4ca8c4
dashboard link: https://syzkaller.appspot.com/bug?extid=d9ae84069cff753e94bf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10642545900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141f2bed900000
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-19 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 9:29 syzbot
2020-09-14 12:15 ` Eric W. Biederman
2020-09-14 12:23 ` Dmitry Vyukov
2020-09-14 12:47 ` Eric W. Biederman
2020-10-19 21:38 ` syzbot [this message]
2020-10-20 6:11 ` 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=000000000000f098f005b20ced50@google.com \
--to=syzbot+d9ae84069cff753e94bf@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=b.zolnierkie@samsung.com \
--cc=christian@brauner.io \
--cc=dan.carpenter@oracle.com \
--cc=dvyukov@google.com \
--cc=ebiederm@xmission.com \
--cc=george.kennedy@oracle.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sandeen@sandeen.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome