syzbot


INFO: task hung in vfs_setxattr (7)

Status: upstream: reported syz repro on 2025/06/05 17:55
Subsystems: xfs
[Documentation on labels]
Reported-by: syzbot+3d0a18cd22695979a7c6@syzkaller.appspotmail.com
First crash: 172d, last: 15d
Cause bisection: failed (error log, bisect log)
  
Discussions (5)
Title Replies (including bot) Last reply
[syzbot] Monthly xfs report (Oct 2025) 0 (1) 2025/10/29 09:50
[syzbot] Monthly xfs report (Sep 2025) 0 (1) 2025/09/27 20:43
[syzbot] Monthly xfs report (Aug 2025) 0 (1) 2025/08/27 08:15
[syzbot] Monthly xfs report (Jun 2025) 0 (1) 2025/06/25 14:15
[syzbot] [xfs?] INFO: task hung in vfs_setxattr (7) 0 (1) 2025/06/05 17:55
Similar bugs (15)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in vfs_setxattr (2) fs 1 1 1983d 1983d 0/29 auto-closed as invalid on 2020/07/28 17:13
linux-5.15 INFO: task hung in vfs_setxattr (2) 1 syz error 1 788d 788d 0/3 auto-obsoleted due to no activity on 2023/12/15 17:11
upstream INFO: task hung in vfs_setxattr (6) bcachefs 1 8 302d 394d 0/29 auto-obsoleted due to no activity on 2025/04/04 18:48
upstream INFO: task hung in vfs_setxattr (5) fs 1 1 504d 504d 0/29 auto-obsoleted due to no activity on 2024/09/15 03:42
android-49 INFO: task hung in vfs_setxattr 1 4 2640d 2666d 0/3 auto-closed as invalid on 2019/02/22 13:09
linux-5.15 INFO: task hung in vfs_setxattr (3) 1 1 553d 553d 0/3 auto-obsoleted due to no activity on 2024/08/06 16:46
upstream INFO: task hung in vfs_setxattr (3) fs 1 syz done error 49 1456d 1875d 0/29 closed as invalid on 2022/02/08 10:51
upstream INFO: task hung in vfs_setxattr fs 1 46 2513d 2673d 0/29 auto-closed as invalid on 2019/06/15 01:37
linux-4.19 INFO: task hung in vfs_setxattr (2) 1 C error 3 1486d 1766d 0/1 upstream: reported C repro on 2021/01/01 10:53
android-414 INFO: task hung in vfs_setxattr 1 1 2389d 2389d 0/1 auto-closed as invalid on 2019/10/16 16:43
linux-5.15 INFO: task hung in vfs_setxattr 1 1 939d 939d 0/3 auto-obsoleted due to no activity on 2023/08/06 19:50
upstream INFO: task hung in vfs_setxattr (4) ext4 1 1 852d 852d 0/29 auto-obsoleted due to no activity on 2023/10/02 09:30
linux-4.19 INFO: task hung in vfs_setxattr 1 3 2185d 2247d 0/1 auto-closed as invalid on 2020/03/08 20:30
android-6-12 INFO: task hung in vfs_setxattr 1 1 109d 109d 0/1 auto-obsoleted due to no activity on 2025/10/14 10:59
android-44 INFO: task hung in vfs_setxattr 1 C 3 2264d 2269d 0/2 public: reported C repro on 2019/08/17 15:36
Last patch testing requests (3)
Created Duration User Patch Repo Result
2025/11/02 11:37 22m retest repro linux-next OK log
2025/11/02 11:37 23m retest repro upstream OK log
2025/11/02 11:37 23m retest repro linux-next OK log

Sample crash report:
INFO: task syz.9.1621:12008 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.9.1621      state:D stack:24712 pid:12008 tgid:12007 ppid:10308  task_flags:0x400140 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5325 [inline]
 __schedule+0x1798/0x4cc0 kernel/sched/core.c:6929
 __schedule_loop kernel/sched/core.c:7011 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:7026
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7083
 rwsem_down_write_slowpath+0x872/0xfe0 kernel/locking/rwsem.c:1185
 __down_write_common kernel/locking/rwsem.c:1317 [inline]
 __down_write kernel/locking/rwsem.c:1326 [inline]
 down_write+0x1ab/0x1f0 kernel/locking/rwsem.c:1591
 inode_lock include/linux/fs.h:980 [inline]
 vfs_setxattr+0x144/0x2f0 fs/xattr.c:320
 do_setxattr fs/xattr.c:636 [inline]
 filename_setxattr+0x274/0x600 fs/xattr.c:665
 path_setxattrat+0x364/0x3a0 fs/xattr.c:713
 __do_sys_setxattr fs/xattr.c:747 [inline]
 __se_sys_setxattr fs/xattr.c:743 [inline]
 __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:743
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f06d6f8eec9
RSP: 002b:00007f06d7ec1038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f06d71e5fa0 RCX: 00007f06d6f8eec9
RDX: 0000200000000340 RSI: 0000200000000140 RDI: 0000200000000100
RBP: 00007f06d7011f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000700 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f06d71e6038 R14: 00007f06d71e5fa0 R15: 00007ffd6d685928
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13d320 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13d320 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff8e13d320 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
3 locks held by kworker/u8:5/1036:
 #0: ffff88814cded948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
 #0: ffff88814cded948 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3346
 #1: ffffc9000399fba0 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
 #1: ffffc9000399fba0 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3346
 #2: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_verify_work+0x19/0x30 net/ipv6/addrconf.c:4734
2 locks held by getty/5582:
 #0: ffff88814df4d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by kworker/0:3/5825:
 #0: ffff88813ff11948 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
 #0: ffff88813ff11948 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3346
 #1: ffffc90003fdfba0 (free_ipc_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
 #1: ffffc90003fdfba0 (free_ipc_work){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3346
 #2: ffffffff8e142db8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:343 [inline]
 #2: ffffffff8e142db8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x3b9/0x730 kernel/rcu/tree_exp.h:957
3 locks held by kworker/1:5/5931:
3 locks held by kworker/u8:11/6115:
 #0: ffff88813ff29948 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
 #0: ffff88813ff29948 ((wq_completion)events_unbound#2){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3346
 #1: ffffc9000b077ba0 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
 #1: ffffc9000b077ba0 ((linkwatch_work).work){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3346
 #2: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: linkwatch_event+0xe/0x60 net/core/link_watch.c:303
4 locks held by syz-executor/8193:
 #0: ffff888064eb0dc8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:499 [inline]
 #0: ffff888064eb0dc8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x212/0x510 net/bluetooth/hci_core.c:2715
 #1: ffff888064eb00b8 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x66a/0x1330 net/bluetooth/hci_sync.c:5291
 #2: ffffffff8f648f68 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:2118 [inline]
 #2: ffffffff8f648f68 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_conn_hash_flush+0xa1/0x230 net/bluetooth/hci_conn.c:2602
 #3: ffff88802f59b338 (&conn->lock#2){+.+.}-{4:4}, at: l2cap_conn_del+0x70/0x680 net/bluetooth/l2cap_core.c:1762
2 locks held by kbnepd bnep0/10802:
 #0: ffffffff8f671150 (bnep_session_sem){+.+.}-{4:4}, at: bnep_session+0x2940/0x2b40 net/bluetooth/bnep/core.c:522
 #1: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #1: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_dev_lock+0x257/0x2f0 net/core/dev.c:2142
2 locks held by syz.9.1621/12008:
 #0: ffff88802419a420 (sb_writers#31){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:508
 #1: ffff888052637b30 (&sb->s_type->i_mutex_key#36){++++}-{4:4}, at: inode_lock include/linux/fs.h:980 [inline]
 #1: ffff888052637b30 (&sb->s_type->i_mutex_key#36){++++}-{4:4}, at: vfs_setxattr+0x144/0x2f0 fs/xattr.c:320
4 locks held by syz.9.1621/12051:
 #0: ffff88802419a420 (sb_writers#31){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:508
 #1: ffff888052637b30 (&sb->s_type->i_mutex_key#36){++++}-{4:4}, at: inode_lock include/linux/fs.h:980 [inline]
 #1: ffff888052637b30 (&sb->s_type->i_mutex_key#36){++++}-{4:4}, at: vfs_setxattr+0x144/0x2f0 fs/xattr.c:320
 #2: ffff88802419a610 (sb_internal#5){.+.+}-{0:0}, at: xfs_trans_alloc+0xd7/0x980 fs/xfs/xfs_trans.c:256
 #3: ffff888052637918 (&xfs_nondir_ilock_class){++++}-{4:4}, at: xfs_trans_alloc_inode+0x161/0x4a0 fs/xfs/xfs_trans.c:1082
3 locks held by syz.2.1723/12347:
 #0: ffff88804ba58dc8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:499 [inline]
 #0: ffff88804ba58dc8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x212/0x510 net/bluetooth/hci_core.c:2715
 #1: ffff88804ba580b8 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x66a/0x1330 net/bluetooth/hci_sync.c:5291
 #2: ffffffff8e142db8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:343 [inline]
 #2: ffffffff8e142db8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x3b9/0x730 kernel/rcu/tree_exp.h:957
6 locks held by kworker/u8:16/13576:
 #0: ffff88801aa97148 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
 #0: ffff88801aa97148 ((wq_completion)netns){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x17b0 kernel/workqueue.c:3346
 #1: ffffc9000ea17ba0 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
 #1: ffffc9000ea17ba0 (net_cleanup_work){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x17b0 kernel/workqueue.c:3346
 #2: ffffffff8f4d2d30 (pernet_ops_rwsem){++++}-{4:4}, at: cleanup_net+0xf7/0x820 net/core/net_namespace.c:669
 #3: ffff8880643da0e8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:914 [inline]
 #3: ffff8880643da0e8 (&dev->mutex){....}-{4:4}, at: devl_dev_lock net/devlink/devl_internal.h:108 [inline]
 #3: ffff8880643da0e8 (&dev->mutex){....}-{4:4}, at: devlink_pernet_pre_exit+0x10a/0x3d0 net/devlink/core.c:506
 #4: ffff8880643db250 (&devlink->lock_key#5){+.+.}-{4:4}, at: devl_lock net/devlink/core.c:276 [inline]
 #4: ffff8880643db250 (&devlink->lock_key#5){+.+.}-{4:4}, at: devl_dev_lock net/devlink/devl_internal.h:109 [inline]
 #4: ffff8880643db250 (&devlink->lock_key#5){+.+.}-{4:4}, at: devlink_pernet_pre_exit+0x11c/0x3d0 net/devlink/core.c:506
 #5: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: nsim_destroy+0xe5/0x670 drivers/net/netdevsim/netdev.c:1166
2 locks held by syz-executor/13617:
 #0: ffffffff8f9e4f70 (&ops->srcu#2){.+.+}-{0:0}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8f9e4f70 (&ops->srcu#2){.+.+}-{0:0}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff8f9e4f70 (&ops->srcu#2){.+.+}-{0:0}, at: rtnl_link_ops_get+0x23/0x250 net/core/rtnetlink.c:570
 #1: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #1: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline]
 #1: ffffffff8f4dfbc8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x8e9/0x1c80 net/core/rtnetlink.c:4064
3 locks held by syz.8.2113/13632:
 #0: ffff888023c78dc8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_dev_do_close net/bluetooth/hci_core.c:499 [inline]
 #0: ffff888023c78dc8 (&hdev->req_lock){+.+.}-{4:4}, at: hci_unregister_dev+0x212/0x510 net/bluetooth/hci_core.c:2715
 #1: ffff888023c780b8 (&hdev->lock){+.+.}-{4:4}, at: hci_dev_close_sync+0x66a/0x1330 net/bluetooth/hci_sync.c:5291
 #2: ffffffff8f648f68 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:2118 [inline]
 #2: ffffffff8f648f68 (hci_cb_list_lock){+.+.}-{4:4}, at: hci_conn_hash_flush+0xa1/0x230 net/bluetooth/hci_conn.c:2602

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:332 [inline]
 watchdog+0xf60/0xfa0 kernel/hung_task.c:495
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 13636 Comm: syz.1.2117 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__debug_check_no_obj_freed lib/debugobjects.c:1089 [inline]
RIP: 0010:debug_check_no_obj_freed+0x205/0x470 lib/debugobjects.c:1129
Code: 00 ff c3 48 8b 44 24 18 49 89 c7 48 85 c0 0f 84 45 02 00 00 4d 89 fe 49 c1 ee 03 48 b8 00 00 00 00 00 fc ff df 41 80 3c 06 00 <74> 08 4c 89 ff e8 71 d4 8b fd 49 8b 07 48 89 44 24 18 4d 8d 67 18
RSP: 0018:ffffc9000dde7818 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 0000000000000001 RCX: dffffc0000000001
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc9000dde7700
RBP: ffffea0001557b90 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52001bbcee0 R12: ffff888056488b08
R13: ffffc90017724000 R14: 1ffff1100a074a07 R15: ffff8880503a5038
FS:  0000000000000000(0000) GS:ffff888125e0f000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000404030 CR3: 000000000df38000 CR4: 0000000000350ef0
Call Trace:
 <TASK>
 remove_vm_area+0x1d3/0x300 mm/vmalloc.c:3297
 vfree+0x63/0x400 mm/vmalloc.c:3420
 kcov_put kernel/kcov.c:439 [inline]
 kcov_close+0x28/0x50 kernel/kcov.c:535
 __fput+0x44c/0xa70 fs/file_table.c:468
 task_work_run+0x1d4/0x260 kernel/task_work.c:227
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0x6b5/0x2300 kernel/exit.c:966
 do_group_exit+0x21c/0x2d0 kernel/exit.c:1107
 get_signal+0x1285/0x1340 kernel/signal.c:3034
 arch_do_signal_or_restart+0xa0/0x790 arch/x86/kernel/signal.c:337
 exit_to_user_mode_loop+0x72/0x130 kernel/entry/common.c:40
 exit_to_user_mode_prepare include/linux/irq-entry-common.h:225 [inline]
 syscall_exit_to_user_mode_work include/linux/entry-common.h:175 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:210 [inline]
 do_syscall_64+0x2bd/0xfa0 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fe5b898eec9
Code: Unable to access opcode bytes at 0x7fe5b898ee9f.
RSP: 002b:00007fe5b97f9038 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: 0000000000010106 RBX: 00007fe5b8be6090 RCX: 00007fe5b898eec9
RDX: 0000000000010106 RSI: 00002000000000c0 RDI: 0000000000000004
RBP: 00007fe5b8a11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fe5b8be6128 R14: 00007fe5b8be6090 R15: 00007ffcaf453a68
 </TASK>

Crashes (53):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/11 17:14 upstream 0739473694c4 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/04 07:48 upstream 9b0d551bcc05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/03 18:32 upstream e406d57be7bd 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/29 06:29 upstream 8f9736633f8c 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/26 19:36 upstream 4ff71af020ae 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/25 20:01 upstream bf40f4b87761 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/16 03:54 upstream 46a51f4f5eda e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/15 13:57 upstream f83ec76bf285 e2beed91 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/15 08:05 upstream f83ec76bf285 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/11 15:09 upstream 7aac71907bde fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/07 15:30 upstream b236920731dd d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/08/21 14:37 upstream 41cd3fd15263 0b9605c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/08/10 09:26 upstream 561c80369df0 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/08/03 18:38 upstream 186f3edfdd41 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/31 16:31 upstream 260f6f4fda93 0c075d67 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/26 20:36 upstream 5f33ebd2018c fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/23 10:40 upstream 89be9a83ccf1 e1dd4f22 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/23 05:45 upstream 89be9a83ccf1 e1dd4f22 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/11 13:39 upstream bc9ff192a6c9 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/01 17:48 upstream 66701750d556 ffe4b334 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/18 15:03 upstream 52da431bf03b ca631f70 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/09 21:18 upstream 19272b37aa4f 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/02 20:25 upstream cd2e103d57e5 b396b4bf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/27 15:52 upstream 914873bc7df9 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/16 20:36 upstream 3c21441eeffc f41472b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/14 08:19 upstream 405e6c37c89e 7344edeb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/19 07:55 linux-next 93f3bab4310d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/18 17:04 linux-next 93f3bab4310d 1c8c8cd8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/13 11:18 linux-next 2b763d465239 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/11 14:47 linux-next 2b763d465239 ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/06 01:43 linux-next 47a8d4b89844 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/05 21:21 linux-next 47a8d4b89844 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/05 15:42 linux-next 47a8d4b89844 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/10/01 10:58 linux-next 3b9b1f8df454 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/07 08:58 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/07 05:27 linux-next be5d4872e528 d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/05 01:06 linux-next 4ac65880ebca d291dd2d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/09/03 18:28 linux-next 5d50cf9f7cf2 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/08/26 13:54 linux-next 7fa4d8dc380f bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/08/13 15:34 linux-next 2674d1eadaa2 22ec1469 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/08/03 08:59 linux-next 84b92a499e7e 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/20 18:05 linux-next d086c886ceb9 7117feec .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/07/08 10:20 linux-next 26ffb3d6f02c 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/25 20:01 linux-next 1b152eeca84a 26d77996 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/25 13:10 linux-next 1b152eeca84a 26d77996 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/08 08:28 linux-next 475c850a7fdd 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/02 10:36 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 18:10 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 17:34 linux-next 3a83b350b5be 3d2f584d .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 14:23 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/06/01 09:10 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
2025/05/30 22:03 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in vfs_setxattr
* Struck through repros no longer work on HEAD.