From: syzbot <syzbot+75867c44841cb6373570@syzkaller.appspotmail.com>
To: Markus.Elfring@web.de, casey@schaufler-ca.com, dancol@google.com,
hdanton@sina.com, jmorris@namei.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
stephen.smalley.work@gmail.com, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: KASAN: use-after-free Read in userfaultfd_release (2)
Date: Mon, 13 Jul 2020 08:34:06 -0700 [thread overview]
Message-ID: <000000000000cfc8ff05aa546b84@google.com> (raw)
In-Reply-To: <0000000000001bbb6705aa49635a@google.com>
syzbot has bisected this bug to:
commit d08ac70b1e0dc71ac2315007bcc3efb283b2eae4
Author: Daniel Colascione <dancol@google.com>
Date: Wed Apr 1 21:39:03 2020 +0000
Wire UFFD up to SELinux
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14a79d13100000
start commit: 89032636 Add linux-next specific files for 20200708
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16a79d13100000
console output: https://syzkaller.appspot.com/x/log.txt?x=12a79d13100000
kernel config: https://syzkaller.appspot.com/x/.config?x=64a250ebabc6c320
dashboard link: https://syzkaller.appspot.com/bug?extid=75867c44841cb6373570
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13c4c8db100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12cbb68f100000
Reported-by: syzbot+75867c44841cb6373570@syzkaller.appspotmail.com
Fixes: d08ac70b1e0d ("Wire UFFD up to SELinux")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-07-13 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 2:24 KASAN: use-after-free Read in userfaultfd_release (2) syzbot
2020-07-13 15:34 ` syzbot [this message]
2020-07-17 15:05 ` Qian Cai
2020-07-20 15:50 ` Qian Cai
2020-07-21 4:32 ` Stephen Rothwell
[not found] ` <20200713084512.10416-1-hdanton@sina.com>
2020-07-20 16:00 ` Al Viro
2020-07-20 23:46 ` Daniel Colascione
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=000000000000cfc8ff05aa546b84@google.com \
--to=syzbot+75867c44841cb6373570@syzkaller.appspotmail.com \
--cc=Markus.Elfring@web.de \
--cc=casey@schaufler-ca.com \
--cc=dancol@google.com \
--cc=hdanton@sina.com \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.