Re: possible deadlock in __do_page_fault (2)

Re: possible deadlock in __do_page_fault (2)

[Eric Biggers]

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