syzbot |
sign-in | mailing list | source | docs |
🐞 Open [1164] 🐞 Fixed [4323] 🐞 Invalid [9667] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes |
Created | Duration | User | Patch | Repo | Result |
---|---|---|---|---|---|
2023/01/09 11:32 | 14m | retest repro | upstream | report log | |
2022/10/11 23:30 | 18m | retest repro | upstream | error | |
2022/10/01 08:30 | 10m | retest repro | upstream | report log |
===================================================== WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected 5.19.0-rc3-syzkaller-00043-g3abc3ae553c7 #0 Not tainted ----------------------------------------------------- syz-executor298/3612 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire: ffffffff8c80a058 (tasklist_lock){.+.+}-{2:2}, at: send_sigio+0xbe/0x300 fs/fcntl.c:791 and this task is already holding: ffff888021360130 (&f->f_owner.lock){....}-{2:2}, at: send_sigio+0x2f/0x300 fs/fcntl.c:777 which would create a new lock dependency: (&f->f_owner.lock){....}-{2:2} -> (tasklist_lock){.+.+}-{2:2} but this new dependency connects a HARDIRQ-irq-safe lock: (&timer->lock){-...}-{2:2}
Manager | Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
ci-upstream-kasan-gce-smack-root | 2022/06/23 07:48 | upstream | 3abc3ae553c7 | 912f5df7 | .config | strace log | report | syz | C | possible deadlock in corrupted | ||
ci-upstream-kasan-gce | 2022/06/02 17:07 | upstream | d1dc87763f40 | 5783034f | .config | strace log | report | syz | C | possible deadlock in corrupted |