syzbot


INFO: task hung in __writeback_inodes_sb_nr (5)

Status: fixed on 2023/02/24 13:50
Subsystems: ext4
[Documentation on labels]
Fix commit: 7d9b1b578d67 ip6mr: fix use-after-free in ip6mr_sk_done()
First crash: 805d, last: 434d
Cause bisection: introduced by (bisect log) :
commit f2f2325ec79970807012dfc9e716cdbb02d9b574
Author: Eric Dumazet <edumazet@google.com>
Date: Fri Feb 4 20:15:46 2022 +0000

  ip6mr: ip6mr_sk_done() can exit early in common cases

Crash: KASAN: use-after-free Read in ip6mr_sk_done (log)
Repro: C syz .config
  
Similar bugs (13)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in __writeback_inodes_sb_nr fs 53 1929d 2192d 0/26 closed as dup on 2018/09/08 15:33
android-49 INFO: task hung in __writeback_inodes_sb_nr 26 2025d 2168d 0/3 auto-closed as invalid on 2019/04/08 13:33
android-414 INFO: task hung in __writeback_inodes_sb_nr 1 1963d 1840d 0/1 auto-closed as invalid on 2019/06/09 16:55
linux-5.15 INFO: task hung in __writeback_inodes_sb_nr origin:lts-only C done 1496 6d03h 414d 0/3 upstream: reported C repro on 2023/03/09 17:32
linux-6.1 INFO: task hung in __writeback_inodes_sb_nr (2) 4 10d 119d 0/3 upstream: reported on 2023/12/30 04:30
linux-4.19 INFO: task hung in __writeback_inodes_sb_nr ext4 4 429d 576d 0/1 upstream: reported on 2022/09/28 21:19
linux-6.1 INFO: task hung in __writeback_inodes_sb_nr 1 253d 253d 0/3 auto-obsoleted due to no activity on 2023/11/26 06:37
upstream INFO: task hung in __writeback_inodes_sb_nr (6) ext4 C done 78 105d 315d 1/26 upstream: reported C repro on 2023/06/17 00:33
upstream INFO: task hung in __writeback_inodes_sb_nr (4) ext4 4 812d 867d 0/26 closed as invalid on 2022/02/08 10:10
upstream INFO: task hung in __writeback_inodes_sb_nr (3) ext4 2 1079d 1176d 0/26 auto-closed as invalid on 2021/08/11 17:49
linux-4.14 INFO: task hung in __writeback_inodes_sb_nr (2) 2 544d 546d 0/1 auto-obsoleted due to no activity on 2023/02/27 15:30
upstream INFO: task hung in __writeback_inodes_sb_nr (2) ext4 1 1361d 1361d 0/26 auto-closed as invalid on 2020/11/03 06:13
linux-4.14 INFO: task hung in __writeback_inodes_sb_nr 1 1427d 1427d 0/1 auto-closed as invalid on 2020/09/27 19:31

Sample crash report:
INFO: task syz-executor317:4016 blocked for more than 143 seconds.
      Not tainted 5.19.0-rc4-syzkaller-00036-gd9b2ba67917c #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor317 state:D stack:25368 pid: 4016 ppid:  3641 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5146 [inline]
 __schedule+0x957/0xe20 kernel/sched/core.c:6458
 schedule+0xeb/0x1b0 kernel/sched/core.c:6530
 wb_wait_for_completion+0x165/0x290 fs/fs-writeback.c:191
 __writeback_inodes_sb_nr+0x2f0/0x3d0 fs/fs-writeback.c:2607
 try_to_writeback_inodes_sb+0xa5/0xd0 fs/fs-writeback.c:2655
 ext4_nonda_switch fs/ext4/inode.c:2932 [inline]
 ext4_da_write_begin+0x243/0x760 fs/ext4/inode.c:2959
 generic_perform_write+0x314/0x610 mm/filemap.c:3779
 ext4_buffered_write_iter+0x114/0x290 fs/ext4/file.c:270
 ext4_file_write_iter+0x9ab/0x1970
 call_write_iter include/linux/fs.h:2058 [inline]
 new_sync_write fs/read_write.c:504 [inline]
 vfs_write+0xa22/0xd40 fs/read_write.c:591
 ksys_write+0x19b/0x2c0 fs/read_write.c:644
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7ff499e55039
RSP: 002b:00007ff4995f9308 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff499ed74a8 RCX: 00007ff499e55039
RDX: 00000000ffffff6a RSI: 0000000020000000 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000012 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff499ed74a0
R13: 00007ff499ea36b4 R14: 0000000000000003 R15: 0000000000022000
 </TASK>
INFO: task syz-executor317:4017 blocked for more than 143 seconds.
      Not tainted 5.19.0-rc4-syzkaller-00036-gd9b2ba67917c #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor317 state:D stack:23424 pid: 4017 ppid:  3641 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5146 [inline]
 __schedule+0x957/0xe20 kernel/sched/core.c:6458
 schedule+0xeb/0x1b0 kernel/sched/core.c:6530
 rwsem_down_write_slowpath+0xe21/0x1370 kernel/locking/rwsem.c:1172
 __down_write_common kernel/locking/rwsem.c:1287 [inline]
 __down_write kernel/locking/rwsem.c:1296 [inline]
 down_write_nested+0x16c/0x180 kernel/locking/rwsem.c:1653
 ext4_move_extents+0x38e/0xf10 fs/ext4/move_extent.c:608
 __ext4_ioctl fs/ext4/ioctl.c:1269 [inline]
 ext4_ioctl+0x30ca/0x4d20 fs/ext4/ioctl.c:1519
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7ff499e55039
RSP: 002b:00007ff4995d8308 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff499ed74b8 RCX: 00007ff499e55039
RDX: 0000000020000180 RSI: 00000000c028660f RDI: 0000000000000024
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff499ed74b0
R13: 00007ff499ea36b4 R14: 00007ff4995d8400 R15: 0000000000022000
 </TASK>
INFO: task syz-executor317:4018 blocked for more than 143 seconds.
      Not tainted 5.19.0-rc4-syzkaller-00036-gd9b2ba67917c #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor317 state:D stack:24440 pid: 4018 ppid:  3641 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5146 [inline]
 __schedule+0x957/0xe20 kernel/sched/core.c:6458
 schedule+0xeb/0x1b0 kernel/sched/core.c:6530
 rwsem_down_write_slowpath+0xe21/0x1370 kernel/locking/rwsem.c:1172
 __down_write_common kernel/locking/rwsem.c:1287 [inline]
 __down_write kernel/locking/rwsem.c:1296 [inline]
 down_write+0x163/0x170 kernel/locking/rwsem.c:1543
 inode_lock include/linux/fs.h:741 [inline]
 process_measurement+0x437/0x1c10 security/integrity/ima/ima_main.c:241
 ima_file_check+0xe7/0x160 security/integrity/ima/ima_main.c:517
 do_open fs/namei.c:3522 [inline]
 path_openat+0x2705/0x2ec0 fs/namei.c:3653
 do_filp_open+0x277/0x4f0 fs/namei.c:3680
 do_sys_openat2+0x13b/0x500 fs/open.c:1278
 do_sys_open fs/open.c:1294 [inline]
 __do_sys_openat fs/open.c:1310 [inline]
 __se_sys_openat fs/open.c:1305 [inline]
 __x64_sys_openat+0x243/0x290 fs/open.c:1305
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x46/0xb0
RIP: 0033:0x7ff499e55039
RSP: 002b:00007ff4995b7308 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007ff499ed74c8 RCX: 00007ff499e55039
RDX: 000000000000275a RSI: 0000000020000280 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 00007ff4995b7700 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ff499ed74c0
R13: 00007ff499ea36b4 R14: 00007ff4995b7400 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/28:
 #0: ffffffff8cb1e820 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:5/1222:
 #0: ffff88801748b938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x796/0xd10 kernel/workqueue.c:2262
 #1: ffffc9000519fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7d0/0xd10 kernel/workqueue.c:2264
 #2: ffff88814ae68bd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1e0/0x3c20 fs/ext4/inode.c:2676
2 locks held by getty/3287:
 #0: ffff888026c73098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
 #1: ffffc90002d162e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6e8/0x1e50 drivers/tty/n_tty.c:2124
1 lock held by syz-executor317/4015:
 #0: ffff88814ae68bd8 (&sbi->s_writepages_rwsem){.+.+}-{0:0}, at: ext4_writepages+0x1e0/0x3c20 fs/ext4/inode.c:2676
4 locks held by syz-executor317/4016:
 #0: ffff8880762560e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x242/0x2e0 fs/file.c:1036
 #1: ffff88814ae66460 (sb_writers#4){.+.+}-{0:0}, at: vfs_write+0x28c/0xd40 fs/read_write.c:587
 #2: ffff88806dc69810 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:741 [inline]
 #2: ffff88806dc69810 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: ext4_buffered_write_iter+0x9e/0x290 fs/ext4/file.c:264
 #3: ffff88814ae660e0 (&type->s_umount_key#31){++++}-{3:3}, at: try_to_writeback_inodes_sb+0x20/0xd0 fs/fs-writeback.c:2652
3 locks held by syz-executor317/4017:
 #0: ffff88814ae66460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write_file+0x5a/0x1f0 fs/namespace.c:437
 #1: ffff88806dc66850 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:741 [inline]
 #1: ffff88806dc66850 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: lock_two_nondirectories+0xdd/0x130 fs/inode.c:1122
 #2: ffff88806dc69810 (&sb->s_type->i_mutex_key#8/4){+.+.}-{3:3}, at: ext4_move_extents+0x38e/0xf10 fs/ext4/move_extent.c:608
2 locks held by syz-executor317/4018:
 #0: ffff88814ae66460 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3b/0x80 fs/namespace.c:393
 #1: ffff88806dc69810 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:741 [inline]
 #1: ffff88806dc69810 (&sb->s_type->i_mutex_key#8){+.+.}-{3:3}, at: process_measurement+0x437/0x1c10 security/integrity/ima/ima_main.c:241

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 5.19.0-rc4-syzkaller-00036-gd9b2ba67917c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 nmi_cpu_backtrace+0x473/0x4a0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x168/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xcf9/0xd40 kernel/hung_task.c:369
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4025 Comm: kworker/u4:1 Not tainted 5.19.0-rc4-syzkaller-00036-gd9b2ba67917c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:rcu_is_watching+0x62/0xa0 kernel/rcu/tree.c:1139
Code: 4c 89 f7 e8 10 9f 69 00 48 c7 c3 50 ab 03 00 49 03 1e 48 89 d8 48 c1 e8 03 42 8a 04 38 84 c0 75 1a 8b 03 65 ff 0d 66 a5 91 7e <74> 08 24 01 5b 41 5e 41 5f c3 e8 1f 8f 8f ff eb f1 89 d9 80 e1 07
RSP: 0018:ffffc9000397f5a0 EFLAGS: 00000082
RAX: 0000000000152ae1 RBX: ffff8880b9b3ab50 RCX: ffff8880225d3b00
RDX: 0000000000000000 RSI: ffffffff8ae996a0 RDI: ffffffff8ae99660
RBP: ffffc9000397f648 R08: dffffc0000000000 R09: fffffbfff1c071de
R10: fffffbfff1c071de R11: 1ffffffff1c071dd R12: ffff888011f18000
R13: dffffc0000000000 R14: ffffffff8c587838 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe7973afb0 CR3: 00000001400fd000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 rcu_read_lock_held_common kernel/rcu/update.c:108 [inline]
 rcu_read_lock_sched_held+0x6b/0x130 kernel/rcu/update.c:123
 trace_tlb_flush+0x78/0x190 include/trace/events/tlb.h:38
 switch_mm_irqs_off+0x5b1/0x900
 use_temporary_mm arch/x86/kernel/alternative.c:962 [inline]
 __text_poke+0x5c2/0x9d0 arch/x86/kernel/alternative.c:1073
 text_poke arch/x86/kernel/alternative.c:1137 [inline]
 text_poke_bp_batch+0x49e/0x970 arch/x86/kernel/alternative.c:1432
 text_poke_flush arch/x86/kernel/alternative.c:1589 [inline]
 text_poke_finish+0x16/0x30 arch/x86/kernel/alternative.c:1596
 arch_jump_label_transform_apply+0x13/0x20 arch/x86/kernel/jump_label.c:146
 static_key_enable_cpuslocked+0x129/0x250 kernel/jump_label.c:177
 static_key_enable+0x16/0x20 kernel/jump_label.c:190
 toggle_allocation_gate+0xbf/0x470 mm/kfence/core.c:811
 process_one_work+0x81c/0xd10 kernel/workqueue.c:2289
 worker_thread+0xb14/0x1330 kernel/workqueue.c:2436
 kthread+0x266/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30
 </TASK>
----------------
Code disassembly (best guess):
   0:	4c 89 f7             	mov    %r14,%rdi
   3:	e8 10 9f 69 00       	callq  0x699f18
   8:	48 c7 c3 50 ab 03 00 	mov    $0x3ab50,%rbx
   f:	49 03 1e             	add    (%r14),%rbx
  12:	48 89 d8             	mov    %rbx,%rax
  15:	48 c1 e8 03          	shr    $0x3,%rax
  19:	42 8a 04 38          	mov    (%rax,%r15,1),%al
  1d:	84 c0                	test   %al,%al
  1f:	75 1a                	jne    0x3b
  21:	8b 03                	mov    (%rbx),%eax
  23:	65 ff 0d 66 a5 91 7e 	decl   %gs:0x7e91a566(%rip)        # 0x7e91a590
* 2a:	74 08                	je     0x34 <-- trapping instruction
  2c:	24 01                	and    $0x1,%al
  2e:	5b                   	pop    %rbx
  2f:	41 5e                	pop    %r14
  31:	41 5f                	pop    %r15
  33:	c3                   	retq
  34:	e8 1f 8f 8f ff       	callq  0xff8f8f58
  39:	eb f1                	jmp    0x2c
  3b:	89 d9                	mov    %ebx,%ecx
  3d:	80 e1 07             	and    $0x7,%cl

Crashes (48):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/06/30 07:46 upstream d9b2ba67917c 1434eec0 .config console log report syz C ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/02/12 04:13 net-next-old 5a8fb33e5305 8b9ca619 .config console log report syz C ci-upstream-net-kasan-gce INFO: task hung in __writeback_inodes_sb_nr
2022/06/30 08:11 linux-next cb71b93c2dc3 1434eec0 .config console log report syz C ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2023/02/18 00:46 upstream ec35307e18ba 3e7039f4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2023/02/17 20:53 upstream ec35307e18ba 3e7039f4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2023/02/15 23:32 upstream e1c04510f521 6be0f1f5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2023/01/30 22:53 upstream 6d796c50f84c 9dfcf09c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2023/01/16 16:09 upstream 5dc4c995db9e a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2023/01/09 13:04 upstream 1fe4fd6f5cad 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/12/26 06:22 upstream 72a85e2b0a1e 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in __writeback_inodes_sb_nr
2022/12/17 14:02 upstream 77856d911a8c 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/12/12 23:59 upstream 830b3c68c1fb 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/11/27 02:07 upstream 644e9524388a 74a66371 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/11/03 06:42 upstream b229b6ca5abb 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/11/03 03:18 upstream b229b6ca5abb 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/11/02 22:50 upstream b229b6ca5abb 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/31 15:00 upstream b229b6ca5abb 2a71366b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/31 13:47 upstream b229b6ca5abb 2a71366b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/29 03:09 upstream b229b6ca5abb ea12ae9b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/27 19:39 upstream 98555239e4c3 86777b7f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/26 19:32 upstream 4dc12f37a8e9 2159e4d2 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/24 06:48 upstream a70385240892 23bf86af .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/24 04:48 upstream a70385240892 23bf86af .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/22 18:02 upstream 4da34b7d175d c0b80a55 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/21 23:03 upstream e35184f32151 4bfd3c27 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/19 22:30 upstream 55be6084c8e0 b31320fc .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/19 02:38 upstream 55be6084c8e0 b31320fc .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/17 08:15 upstream 55be6084c8e0 67cb024c .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/16 19:01 upstream 55be6084c8e0 67cb024c .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/15 17:44 upstream 55be6084c8e0 67cb024c .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/14 20:19 upstream 55be6084c8e0 4954e4b2 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/14 14:04 upstream 55be6084c8e0 4954e4b2 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/14 02:03 upstream 55be6084c8e0 adf90437 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/13 20:25 upstream 55be6084c8e0 adf90437 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/11 00:34 upstream 4899a36f91a9 aea5da89 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/09 15:00 upstream a6afa4199d3d aea5da89 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/09 10:27 upstream a6afa4199d3d aea5da89 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/09 07:27 upstream a6afa4199d3d aea5da89 .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-selinux-root INFO: task hung in __writeback_inodes_sb_nr
2022/06/24 10:02 upstream 92f20ff72066 a5dbd430 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in __writeback_inodes_sb_nr
2022/02/11 22:42 net-next-old 5a8fb33e5305 8b9ca619 .config console log report info ci-upstream-net-kasan-gce INFO: task hung in __writeback_inodes_sb_nr
2022/12/27 15:52 linux-next c76083fac3ba 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/11/22 06:57 linux-next 15f3bff12cf6 1c576c23 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/28 09:28 linux-next 4d48f589d294 86777b7f .config console log report info [disk image] [vmlinux] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/23 00:15 linux-next 4d48f589d294 c0b80a55 .config console log report info [disk image] [vmlinux] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/22 15:10 linux-next 4d48f589d294 c0b80a55 .config console log report info [disk image] [vmlinux] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/21 22:08 linux-next 4d48f589d294 4bfd3c27 .config console log report info [disk image] [vmlinux] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/17 09:50 linux-next 76af7e97f97e 67cb024c .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
2022/10/09 03:26 linux-next aaa11ce2ffc8 aea5da89 .config console log report info [disk image] [vmlinux] ci-upstream-linux-next-kasan-gce-root INFO: task hung in __writeback_inodes_sb_nr
* Struck through repros no longer work on HEAD.