| Date | Name | Commit | Repro | Result |
|---|---|---|---|---|
| 2024/05/03 | upstream (ToT) | f03359bca01b | C | Didn't crash |
syzbot |
sign-in | mailing list | source | docs |
| Date | Name | Commit | Repro | Result |
|---|---|---|---|---|
| 2024/05/03 | upstream (ToT) | f03359bca01b | C | Didn't crash |
| Kernel | Title | Rank 🛈 | Repro | Cause bisect | Fix bisect | Count | Last | Reported | Patched | Status |
|---|---|---|---|---|---|---|---|---|---|---|
| upstream | possible deadlock in scheduler_tick (2) ntfs3 | 4 | C | 10 | 938d | 955d | 23/29 | fixed on 2023/09/28 17:51 | ||
| linux-6.1 | possible deadlock in scheduler_tick origin:upstream missing-backport | 4 | C | done | 237 | 591d | 650d | 3/3 | fixed on 2024/06/26 10:57 | |
| upstream | possible deadlock in scheduler_tick kvm-x86 | 4 | C | error | 99 | 1730d | 1742d | 20/29 | fixed on 2022/03/16 16:02 | |
| upstream | possible deadlock in scheduler_tick (3) bpf net | 4 | C | 1179 | 613d | 650d | 25/29 | fixed on 2024/05/22 23:36 |
=====================================================
WARNING: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
5.15.153-syzkaller #0 Not tainted
-----------------------------------------------------
swapper/0/0 [HC0[0]:SC0[2]:HE0:SE0] is trying to acquire:
ffff88814ae8cb68 (&htab->buckets[i].lock){+...}-{2:2}, at: sock_hash_delete_elem+0xac/0x2f0 net/core/sock_map.c:937
and this task is already holding:
ffff8880b9a3a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
which would create a new lock dependency:
(&rq->__lock){-.-.}-{2:2} -> (&htab->buckets[i].lock){+...}-{2:2}
but this new dependency connects a HARDIRQ-irq-safe lock:
(&rq->__lock){-.-.}-{2:2}
... which became HARDIRQ-irq-safe at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
_raw_spin_lock_nested+0x2d/0x40 kernel/locking/spinlock.c:368
raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
rq_lock kernel/sched/sched.h:1621 [inline]
scheduler_tick+0x97/0x500 kernel/sched/core.c:5296
update_process_times+0x1ca/0x200 kernel/time/timer.c:1793
tick_periodic+0x197/0x210 kernel/time/tick-common.c:100
tick_handle_periodic+0x46/0x150 kernel/time/tick-common.c:112
timer_interrupt+0x4d/0x60 arch/x86/kernel/time.c:57
__handle_irq_event_percpu+0x292/0xa70 kernel/irq/handle.c:156
handle_irq_event_percpu kernel/irq/handle.c:196 [inline]
handle_irq_event+0xff/0x2b0 kernel/irq/handle.c:213
handle_edge_irq+0x245/0xbf0 kernel/irq/chip.c:822
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq arch/x86/kernel/irq.c:231 [inline]
__common_interrupt+0xd7/0x1f0 arch/x86/kernel/irq.c:250
common_interrupt+0x9f/0xc0 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x22/0x40 arch/x86/include/asm/idtentry.h:629
console_unlock+0xe53/0x12b0 kernel/printk/printk.c:2743
vprintk_emit+0xbf/0x150 kernel/printk/printk.c:2268
_printk+0xd1/0x111 kernel/printk/printk.c:2293
spectre_v2_select_mitigation+0x4b9/0x748 arch/x86/kernel/cpu/bugs.c:1626
cpu_select_mitigations+0x3d/0x8f arch/x86/kernel/cpu/bugs.c:151
arch_cpu_finalize_init+0xf/0x81 arch/x86/kernel/cpu/common.c:2253
start_kernel+0x419/0x535 init/main.c:1105
secondary_startup_64_no_verify+0xb1/0xbb
to a HARDIRQ-irq-unsafe lock:
(&htab->buckets[i].lock){+...}-{2:2}
... which became HARDIRQ-irq-unsafe at:
...
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
sock_hash_free+0x14c/0x780 net/core/sock_map.c:1154
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
other info that might help us debug this:
Possible interrupt unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&htab->buckets[i].lock);
local_irq_disable();
lock(&rq->__lock);
lock(&htab->buckets[i].lock);
<Interrupt>
lock(&rq->__lock);
*** DEADLOCK ***
2 locks held by swapper/0/0:
#0: ffff8880b9a3a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
#1: ffffffff8c91f720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x5/0x30 include/linux/rcupdate.h:311
the dependencies between HARDIRQ-irq-safe lock and the holding lock:
-> (&rq->__lock){-.-.}-{2:2} {
IN-HARDIRQ-W at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
_raw_spin_lock_nested+0x2d/0x40 kernel/locking/spinlock.c:368
raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
rq_lock kernel/sched/sched.h:1621 [inline]
scheduler_tick+0x97/0x500 kernel/sched/core.c:5296
update_process_times+0x1ca/0x200 kernel/time/timer.c:1793
tick_periodic+0x197/0x210 kernel/time/tick-common.c:100
tick_handle_periodic+0x46/0x150 kernel/time/tick-common.c:112
timer_interrupt+0x4d/0x60 arch/x86/kernel/time.c:57
__handle_irq_event_percpu+0x292/0xa70 kernel/irq/handle.c:156
handle_irq_event_percpu kernel/irq/handle.c:196 [inline]
handle_irq_event+0xff/0x2b0 kernel/irq/handle.c:213
handle_edge_irq+0x245/0xbf0 kernel/irq/chip.c:822
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq arch/x86/kernel/irq.c:231 [inline]
__common_interrupt+0xd7/0x1f0 arch/x86/kernel/irq.c:250
common_interrupt+0x9f/0xc0 arch/x86/kernel/irq.c:240
asm_common_interrupt+0x22/0x40 arch/x86/include/asm/idtentry.h:629
console_unlock+0xe53/0x12b0 kernel/printk/printk.c:2743
vprintk_emit+0xbf/0x150 kernel/printk/printk.c:2268
_printk+0xd1/0x111 kernel/printk/printk.c:2293
spectre_v2_select_mitigation+0x4b9/0x748 arch/x86/kernel/cpu/bugs.c:1626
cpu_select_mitigations+0x3d/0x8f arch/x86/kernel/cpu/bugs.c:151
arch_cpu_finalize_init+0xf/0x81 arch/x86/kernel/cpu/common.c:2253
start_kernel+0x419/0x535 init/main.c:1105
secondary_startup_64_no_verify+0xb1/0xbb
IN-SOFTIRQ-W at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
_raw_spin_lock_nested+0x2d/0x40 kernel/locking/spinlock.c:368
raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
rq_lock kernel/sched/sched.h:1621 [inline]
ttwu_queue kernel/sched/core.c:3821 [inline]
try_to_wake_up+0x6dd/0x1300 kernel/sched/core.c:4146
call_timer_fn+0x16d/0x560 kernel/time/timer.c:1421
expire_timers kernel/time/timer.c:1466 [inline]
__run_timers+0x67c/0x890 kernel/time/timer.c:1737
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1750
__do_softirq+0x3b3/0x93a kernel/softirq.c:558
invoke_softirq kernel/softirq.c:432 [inline]
__irq_exit_rcu+0x155/0x240 kernel/softirq.c:637
irq_exit_rcu+0x5/0x20 kernel/softirq.c:649
sysvec_apic_timer_interrupt+0x91/0xb0 arch/x86/kernel/apic/apic.c:1096
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:638
native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
default_idle+0xb/0x10 arch/x86/kernel/process.c:717
default_idle_call+0x81/0xc0 kernel/sched/idle.c:112
cpuidle_idle_call kernel/sched/idle.c:194 [inline]
do_idle+0x271/0x670 kernel/sched/idle.c:306
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:403
start_kernel+0x48c/0x535 init/main.c:1138
secondary_startup_64_no_verify+0xb1/0xbb
INITIAL USE at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
_raw_spin_lock_nested+0x2d/0x40 kernel/locking/spinlock.c:368
raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
raw_spin_rq_lock kernel/sched/sched.h:1326 [inline]
_raw_spin_rq_lock_irqsave kernel/sched/sched.h:1345 [inline]
rq_attach_root+0xec/0x440 kernel/sched/topology.c:470
sched_init+0x6a4/0xbdd kernel/sched/core.c:9502
start_kernel+0x1b6/0x535 init/main.c:1007
secondary_startup_64_no_verify+0xb1/0xbb
}
... key at: [<ffffffff8f5dcc40>] sched_init.__key+0x0/0x20
the dependencies between the lock to be acquired
and HARDIRQ-irq-unsafe lock:
-> (&htab->buckets[i].lock){+...}-{2:2} {
HARDIRQ-ON-W at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
sock_hash_free+0x14c/0x780 net/core/sock_map.c:1154
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
INITIAL USE at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
sock_hash_free+0x14c/0x780 net/core/sock_map.c:1154
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
}
... key at: [<ffffffff9178a740>] sock_hash_alloc.__key+0x0/0x20
... acquired at:
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
sock_hash_delete_elem+0xac/0x2f0 net/core/sock_map.c:937
bpf_prog_a8aaa52f2e199321+0x42/0x548
bpf_dispatcher_nop_func include/linux/bpf.h:785 [inline]
__bpf_prog_run include/linux/filter.h:628 [inline]
bpf_prog_run include/linux/filter.h:635 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1880 [inline]
bpf_trace_run3+0x1d1/0x380 kernel/trace/bpf_trace.c:1918
trace_sched_switch include/trace/events/sched.h:220 [inline]
__schedule+0x1e8d/0x45b0 kernel/sched/core.c:6373
schedule_idle+0x4a/0x90 kernel/sched/core.c:6487
do_idle+0x61e/0x670 kernel/sched/idle.c:334
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:403
start_kernel+0x48c/0x535 init/main.c:1138
secondary_startup_64_no_verify+0xb1/0xbb
stack backtrace:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_bad_irq_dependency kernel/locking/lockdep.c:2567 [inline]
check_irq_usage kernel/locking/lockdep.c:2806 [inline]
check_prev_add kernel/locking/lockdep.c:3057 [inline]
check_prevs_add kernel/locking/lockdep.c:3172 [inline]
validate_chain+0x4d01/0x5930 kernel/locking/lockdep.c:3788
__lock_acquire+0x1295/0x1ff0 kernel/locking/lockdep.c:5012
lock_acquire+0x1db/0x4f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x31/0x40 kernel/locking/spinlock.c:178
sock_hash_delete_elem+0xac/0x2f0 net/core/sock_map.c:937
bpf_prog_a8aaa52f2e199321+0x42/0x548
bpf_dispatcher_nop_func include/linux/bpf.h:785 [inline]
__bpf_prog_run include/linux/filter.h:628 [inline]
bpf_prog_run include/linux/filter.h:635 [inline]
__bpf_trace_run kernel/trace/bpf_trace.c:1880 [inline]
bpf_trace_run3+0x1d1/0x380 kernel/trace/bpf_trace.c:1918
trace_sched_switch include/trace/events/sched.h:220 [inline]
__schedule+0x1e8d/0x45b0 kernel/sched/core.c:6373
schedule_idle+0x4a/0x90 kernel/sched/core.c:6487
do_idle+0x61e/0x670 kernel/sched/idle.c:334
cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:403
start_kernel+0x48c/0x535 init/main.c:1138
secondary_startup_64_no_verify+0xb1/0xbb
</TASK>
| Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024/04/06 09:11 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |
| 2024/04/05 20:06 | linux-5.15.y | 9465fef4ae35 | 77230c29 | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |
| 2024/04/04 16:01 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |
| 2024/04/04 02:23 | linux-5.15.y | 9465fef4ae35 | 51c4dcff | .config | console log | report | syz | C | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/01 21:58 | linux-5.15.y | 9465fef4ae35 | 6baf5069 | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |
| 2024/04/01 01:00 | linux-5.15.y | 9465fef4ae35 | 6baf5069 | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |
| 2024/03/27 09:55 | linux-5.15.y | 9465fef4ae35 | 454571b6 | .config | console log | report | syz | C | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/03/16 21:20 | linux-5.15.y | b95c01af2113 | d615901c | .config | console log | report | syz | C | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |
| 2024/04/10 10:52 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/10 08:56 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/10 08:10 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/10 07:02 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/10 04:01 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/10 02:04 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/10 00:46 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/09 23:14 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/09 21:01 | linux-5.15.y | 9465fef4ae35 | 171ec371 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/09 15:41 | linux-5.15.y | 9465fef4ae35 | f3234354 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/09 13:30 | linux-5.15.y | 9465fef4ae35 | f3234354 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/09 08:51 | linux-5.15.y | 9465fef4ae35 | f3234354 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/09 06:40 | linux-5.15.y | 9465fef4ae35 | f3234354 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/09 05:21 | linux-5.15.y | 9465fef4ae35 | f3234354 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/08 22:31 | linux-5.15.y | 9465fef4ae35 | 53df08b6 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/08 19:55 | linux-5.15.y | 9465fef4ae35 | 53df08b6 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/08 17:13 | linux-5.15.y | 9465fef4ae35 | 53df08b6 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/08 15:51 | linux-5.15.y | 9465fef4ae35 | 53df08b6 | .config | console log | report | info | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |||
| 2024/04/08 14:28 | linux-5.15.y | 9465fef4ae35 | 53df08b6 | .config | console log | report | info | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | |||
| 2024/04/08 08:06 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/08 05:55 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/07 21:33 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/07 20:10 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/07 08:00 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/06 23:53 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/06 20:53 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/06 17:54 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/06 16:20 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/06 05:04 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/06 03:27 | linux-5.15.y | 9465fef4ae35 | ca620dd8 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/05 19:18 | linux-5.15.y | 9465fef4ae35 | 77230c29 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/05 14:57 | linux-5.15.y | 9465fef4ae35 | 77230c29 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/05 13:33 | linux-5.15.y | 9465fef4ae35 | 77230c29 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/05 12:32 | linux-5.15.y | 9465fef4ae35 | 77230c29 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/05 11:10 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/05 09:48 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/05 08:18 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/05 05:20 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/05 03:19 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/05 00:43 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/04 22:55 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan | possible deadlock in scheduler_tick | ||
| 2024/04/04 20:20 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/04 19:10 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick | ||
| 2024/04/04 18:50 | linux-5.15.y | 9465fef4ae35 | 0ee3535e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-linux-5-15-kasan-perf | possible deadlock in scheduler_tick |