From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+606e524a3ca9617cf8c0@syzkaller.appspotmail.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: possible deadlock in __do_page_fault (2)
Date: Sun, 23 Jun 2019 15:18:07 -0700 [thread overview]
Message-ID: <20190623221807.GF772@sol.localdomain> (raw)
In-Reply-To: <1559678925.4237.2.camel@linux.ibm.com>
On Tue, Jun 04, 2019 at 04:08:45PM -0400, Mimi Zohar wrote:
> On Mon, 2019-06-03 at 15:04 -0700, syzbot wrote:
> > 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
>
> Thank you for the report.
>
> Mimi
>
This patch was dropped from linux-next, so let's invalidate this bug report.
#syz invalid
- Eric
next prev parent reply other threads:[~2019-06-24 2:37 UTC|newest]
Thread overview: 6+ 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
2019-06-04 20:08 ` Mimi Zohar
2019-06-23 22:18 ` Eric Biggers [this message]
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=20190623221807.GF772@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=syzbot+606e524a3ca9617cf8c0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--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 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.