Re: possible deadlock in process_measurement (2)

2021-01-05 Thread Dmitry Vyukov
On Sun, Jan 3, 2021 at 12:08 AM syzbot wrote: > > syzbot suspects this issue was fixed by commit: > > commit 15a8d68e9dc23dc9def4bd7e9563db60f4f86580 > Author: Wei Yang > Date: Tue Oct 13 23:56:33 2020 + > > mm/hugetlb: a page from buddy is not on any list > > bisection log: https://sy

Re: possible deadlock in process_measurement (2)

2021-01-02 Thread syzbot
syzbot suspects this issue was fixed by commit: commit 15a8d68e9dc23dc9def4bd7e9563db60f4f86580 Author: Wei Yang Date: Tue Oct 13 23:56:33 2020 + mm/hugetlb: a page from buddy is not on any list bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13612350d0 start commit:

Re: possible deadlock in process_measurement (2)

2020-06-27 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:1590a2e1 Merge tag 'acpi-5.8-rc3' of git://git.kernel.org/.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=164b959b10 kernel config: https://syzkaller.appspot.com/x/.config?x=20c9076

Re: possible deadlock in process_measurement

2019-07-15 Thread Eric Biggers
for mprotect, or both?  Please Cc the > > overlay mailing list on the overlay aspect. > > AFAICS, syzbot boots all kernels with "ima_policy=tcb" on the command line. > And I don't think anything in userspace changes the IMA policy. > > It's not unus

Re: possible deadlock in process_measurement

2019-07-11 Thread Mimi Zohar
Hi Eric, > > the existing dependency chain (in reverse order) is: > > > > -> #1 (&mm->mmap_sem#2){}: > > down_read+0x3f/0x1e0 kernel/locking/rwsem.c:24 > > get_user_pages_unlocked+0xfc/0x4a0 mm/gup.c:1174 > > __gup_longterm_unlocked mm/gup.c:2193 [inline] > > g

Re: possible deadlock in process_measurement

2019-07-11 Thread Eric Biggers
in userspace changes the IMA policy. It's not unusual for multiple underlying bugs to get mixed into the same syzbot bug. syzbot doesn't know that one "possible deadlock in process_measurement" is different from another. "Last occurred" is for any crash that appeare

Re: possible deadlock in process_measurement

2019-07-11 Thread Mimi Zohar
Hi Eric, On Mon, 2019-06-03 at 09:35 -0700, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit:3c09c195 Add linux-next specific files for 20190531 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=10f61a0ea0 > k

Re: possible deadlock in process_measurement

2019-07-11 Thread Mimi Zohar
Hi Eric, On Mon, 2019-06-03 at 09:35 -0700, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit:3c09c195 Add linux-next specific files for 20190531 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=10f61a0ea0 > k

Re: possible deadlock in process_measurement

2019-06-03 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:3c09c195 Add linux-next specific files for 20190531 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=10f61a0ea0 kernel config: https://syzkaller.appspot.com/x/.config?x=6cfb24468280c

possible deadlock in process_measurement

2018-10-15 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:bab5c80b2110 Merge tag 'armsoc-fixes-4.19' of git://git.ke.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=138e5f7640 kernel config: https://syzkaller.appspot.com/x/.config?x=88e9a8a39dc0be2d da