From: syzbot <syzbot+606e524a3ca9617cf8c0@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, hdanton@sina.com, jmorris@namei.org,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
zohar@linux.ibm.com
Subject: Re: possible deadlock in __do_page_fault (2)
Date: Mon, 03 Jun 2019 15:04:00 -0700 [thread overview]
Message-ID: <000000000000a7a51a058a728a6c@google.com> (raw)
In-Reply-To: <000000000000fa91e1058a358cd5@google.com>
syzbot has bisected this bug to:
commit 69d61f577d147b396be0991b2ac6f65057f7d445
Author: Mimi Zohar <zohar@linux.ibm.com>
Date: Wed Apr 3 21:47:46 2019 +0000
ima: verify mprotect change is consistent with mmap policy
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16461c5aa00000
start commit: 3c09c195 Add linux-next specific files for 20190531
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=15461c5aa00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11461c5aa00000
kernel config: https://syzkaller.appspot.com/x/.config?x=6cfb24468280cd5c
dashboard link: https://syzkaller.appspot.com/bug?extid=606e524a3ca9617cf8c0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10572ca6a00000
Reported-by: syzbot+606e524a3ca9617cf8c0@syzkaller.appspotmail.com
Fixes: 69d61f577d14 ("ima: verify mprotect change is consistent with mmap
policy")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-06-03 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 21:18 possible deadlock in __do_page_fault (2) syzbot
2019-06-03 15:15 ` syzbot
2019-06-03 22:04 ` syzbot [this message]
2019-06-04 20:08 ` Mimi Zohar
2019-06-04 20:07 ` syzbot
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=000000000000a7a51a058a728a6c@google.com \
--to=syzbot+606e524a3ca9617cf8c0@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=hdanton@sina.com \
--cc=jmorris@namei.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=zohar@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).