Title | Replies (including bot) | Last reply |
---|---|---|
[syzbot] INFO: task hung in lock_metapage | 0 (1) | 2022/10/26 22:58 |
syzbot |
sign-in | mailing list | source | docs |
🐞 Open [941] ≡ Subsystems 🐞 Fixed [5127] 🐞 Invalid [12267] ⬇ Missing Backports [84] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes | 💬 Send us feedback |
Title | Replies (including bot) | Last reply |
---|---|---|
[syzbot] INFO: task hung in lock_metapage | 0 (1) | 2022/10/26 22:58 |
Created | Duration | User | Patch | Repo | Result |
---|---|---|---|---|---|
2024/03/04 23:44 | 15m | retest repro | upstream | report log | |
2024/01/27 11:16 | 22m | retest repro | upstream | OK log | |
2024/01/25 08:03 | 23m | retest repro | upstream | OK log | |
2023/12/23 12:54 | 18m | retest repro | upstream | report log | |
2023/11/15 04:17 | 2h53m | retest repro | upstream | report log | |
2023/11/15 04:17 | 33m | retest repro | upstream | report log | |
2023/11/15 00:40 | 40m | retest repro | linux-next | OK log | |
2023/11/15 00:40 | 23m | retest repro | linux-next | OK log | |
2023/11/15 00:40 | 23m | retest repro | linux-next | OK log | |
2023/09/26 03:39 | 17m | retest repro | upstream | report log |
Created | Duration | User | Patch | Repo | Result |
---|---|---|---|---|---|
2024/02/01 15:58 | 12h04m | bisect fix | upstream | error job log (0) | |
2023/07/18 00:12 | 1h40m | bisect fix | upstream | job log (0) log | |
2023/06/04 10:17 | 31m | bisect fix | upstream | job log (0) log | |
2023/05/04 22:11 | 29m | bisect fix | upstream | job log (0) log | |
2023/04/04 21:39 | 31m | bisect fix | upstream | job log (0) log | |
2023/01/27 14:55 | 31m | bisect fix | upstream | job log (0) log |
INFO: task jfsCommit:109 blocked for more than 143 seconds. Not tainted 6.8.0-rc5-syzkaller #0 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:jfsCommit state:D stack:25080 pid:109 tgid:109 ppid:2 flags:0x00004000 Call Trace: <TASK> context_switch kernel/sched/core.c:5400 [inline] __schedule+0x177f/0x49a0 kernel/sched/core.c:6727 __schedule_loop kernel/sched/core.c:6802 [inline] schedule+0x149/0x260 kernel/sched/core.c:6817 io_schedule+0x8c/0x110 kernel/sched/core.c:9023 __lock_metapage fs/jfs/jfs_metapage.c:50 [inline] lock_metapage+0x254/0x370 fs/jfs/jfs_metapage.c:64 __get_metapage+0x513/0x1050 fs/jfs/jfs_metapage.c:639 diIAGRead+0xcb/0x140 fs/jfs/jfs_imap.c:2669 diFree+0xa7e/0x2fb0 fs/jfs/jfs_imap.c:956 jfs_evict_inode+0x32d/0x440 fs/jfs/inode.c:156 evict+0x2a8/0x630 fs/inode.c:665 txUpdateMap+0x829/0x9f0 fs/jfs/jfs_txnmgr.c:2367 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline] jfs_lazycommit+0x47f/0xb70 fs/jfs/jfs_txnmgr.c:2733 kthread+0x2ef/0x390 kernel/kthread.c:388 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242 </TASK> Showing all locks held in the system: 1 lock held by khungtaskd/29: #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:298 [inline] #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:750 [inline] #0: ffffffff8e130ae0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6614 2 locks held by jfsCommit/109: #0: ffff8880298f8920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:886 #1: ffff88805f692638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x398/0x2fb0 fs/jfs/jfs_imap.c:891 2 locks held by getty/4816: #0: ffff88802aeb30a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243 #1: ffffc90002efe2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6b4/0x1e10 drivers/tty/n_tty.c:2201 ============================================= NMI backtrace for cpu 1 CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline] check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline] watchdog+0xfaf/0xff0 kernel/hung_task.c:379 kthread+0x2ef/0x390 kernel/kthread.c:388 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:242 </TASK> Sending NMI from CPU 1 to CPUs 0: NMI backtrace for cpu 0 CPU: 0 PID: 5673 Comm: syz-executor337 Not tainted 6.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 RIP: 0033:0x7f4bea23dcf8 Code: 85 ed 74 33 66 0f 1f 44 00 00 48 39 f0 72 1b 4d 8b 07 49 89 c1 49 29 f1 47 0f b6 0c 08 45 84 c9 74 08 45 88 0c 00 49 8b 47 10 <48> 83 c0 01 49 89 47 10 83 e9 01 73 d3 41 81 fe 00 01 00 00 0f 85 RSP: 002b:00007ffee5537b40 EFLAGS: 00000246 RAX: 00000000003e8a20 RBX: 00007ffee5537be0 RCX: 0000000000000089 RDX: 0000000000000055 RSI: 0000000000000001 RDI: 00007ffee5537c80 RBP: 0000000000000102 R08: 00007f4be1e00000 R09: 0000000000000000 R10: 0000000000000000 R11: 00007ffee5537bf0 R12: 0000000000000001 R13: 00007f4bea2c1000 R14: 0000000000000000 R15: 00007ffee5537c80 FS: 000055555735a380 GS: 0000000000000000
Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets (help?) | Manager | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2024/02/19 23:23 | upstream | b401b621758e | 3af7dd65 | .config | strace log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci2-upstream-fs | INFO: task hung in lock_metapage | |
2023/02/12 19:57 | upstream | f339c2597ebb | 93e26d60 | .config | strace log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci-upstream-kasan-gce-root | INFO: task hung in lock_metapage | |
2023/07/28 09:12 | upstream | 57012c57536f | 92476829 | .config | strace log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci-upstream-kasan-gce-selinux-root | INFO: task hung in lock_metapage | |
2022/10/22 22:51 | upstream | 4da34b7d175d | c0b80a55 | .config | strace log | report | syz | C | [disk image] [vmlinux] [mounted in repro] | ci-upstream-kasan-gce-root | INFO: task hung in lock_metapage | |
2023/03/05 21:39 | linux-next | 1acf39ef8f14 | f8902b57 | .config | strace log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci-upstream-linux-next-kasan-gce-root | INFO: task hung in lock_metapage | |
2023/02/13 06:11 | linux-next | 38d2b86a665b | 93e26d60 | .config | strace log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci-upstream-linux-next-kasan-gce-root | INFO: task hung in lock_metapage | |
2022/11/20 15:27 | linux-next | 15f3bff12cf6 | 5bb70014 | .config | strace log | report | syz | C | [disk image] [vmlinux] [kernel image] [mounted in repro] | ci-upstream-linux-next-kasan-gce-root | INFO: task hung in lock_metapage | |
2024/03/09 16:08 | upstream | 10d48d70e82d | 6ee49f2e | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2024/02/19 19:59 | upstream | b401b621758e | 3af7dd65 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2024/02/14 05:36 | upstream | 7e90b5c295ec | d902085f | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/12/09 10:44 | upstream | f2e8a57ee903 | 28b24332 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/12/02 02:02 | upstream | 994d5c58e50e | f819d6f7 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/11/20 09:01 | upstream | eb3479bc23fa | cb976f63 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/11/19 20:15 | upstream | 037266a5f723 | cb976f63 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/11/19 15:35 | upstream | 037266a5f723 | cb976f63 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/10/31 15:29 | upstream | 5a6a09e97199 | 58499c95 | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage | ||
2023/10/27 05:56 | upstream | 3a568e3a961b | bf285f0c | .config | console log | report | info | [disk image] [vmlinux] [kernel image] | ci2-upstream-fs | INFO: task hung in lock_metapage |