From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ot1-f77.google.com (mail-ot1-f77.google.com [209.85.210.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3928F13790B for ; Sat, 9 May 2026 07:38:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.77 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778312321; cv=none; b=RS90bWBZm+X84mWVXdQz7Onsw3T4DyAU7mIbbOPOexFtkTS/biIirzGSDomCCf+CYI2OWW4nNYdyM45EhwgiJOqVHlYL+RcSUvjL/gYfqspmyYPwtPHUFSJ2U9G5yfjeWQ/QuvlvVuEfHhhrjPug77kjYBLGxSsH5q6+3ePuXVw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778312321; c=relaxed/simple; bh=I7ozXL+342ByxsaRA1eQEEqbh63v8rl/0v5T7O1tkpo=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To:Cc: Content-Type; b=lHyLg1WGuVWjj/X1tByh8hH7RridHs9CiImtaXLcvyGDr2ITkddl0ip65/dfc+/6cmunXTnmMJ24SV/ofwWz4bxh0K30m21IuDe6DtblZkmDNXhkokwhvTwIP6oHSdCYkEyDKSOzCRh3DRKfEDiTfMLY5AGKpnSCCDLR1XE8Xx4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.210.77 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-ot1-f77.google.com with SMTP id 46e09a7af769-7e1f3a293aeso6260882a34.2 for ; Sat, 09 May 2026 00:38:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778312318; x=1778917118; h=cc:to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=1qZKnZyBItcdwkG79Wp4Fz2njuN3jbB7XLYY78D3QEY=; b=NvOfpO3JMZMn3fAGyySpRRcIzWG5E54b7Kx7wR0wQW4wGF45BZFfnH4FetvarYabSt vDIhxYznLm/Uj0RsUejtWD8NBuLYQIqrJx07NAGMQ4OsPHEcSwNhQo4NE9ZCUheepEqK f19ZzQFdUN7B+tTRM4OWJeDNcWK6ysSPm1z7UUi70+y5AMOn5TzIJfTs3oGk4rRPh5YI c+3In6PiFucYfsKGhcBtQo9Tt9EBpXcPHwtwfi6r51C9Pl/nsdJRC7QoUDKfTOx2Ffj3 gYfxLpSyLM98CVtphArZhxqu7PyAJXGPaRJAyz0RIn+G1t7cyxPe3bmXhJZldJ5Dwt0I VqSg== X-Forwarded-Encrypted: i=1; AFNElJ+esqb17rlA3+JbLfAWFTHjj7JkBS7aQbzd1d63xW51g9JseItk6A3eL0PrB7UyCgEycYKaTXwjF/r377Y=@vger.kernel.org X-Gm-Message-State: AOJu0YyjV3J+J/MZP2mTU0aNXAHdJxQ+eyMcrUxABNVarNLOrW3Gc1rT UG77iioDP/sogkH6/Gl3Zvdjseqpv7nR1wBsKJDzd+yE9kRF9EjyhYw+E37nS/itftcD8+xUAwn q5lpV5k1rMPIvhJ/lrbkHeXjsFX+zhibGLcVe0iX6ocRhpHAkfdNwf3xsgBA= Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a4a:e918:0:b0:67e:3f0d:4235 with SMTP id 006d021491bc7-69998c9f74emr9200241eaf.11.1778312318267; Sat, 09 May 2026 00:38:38 -0700 (PDT) Date: Sat, 09 May 2026 00:38:38 -0700 In-Reply-To: <319ee859-7a9a-4838-ac3c-f0e04ad9cda3@windriver.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69fee47e.a00a0220.1c3806.0006.GAE@google.com> Subject: Re: [syzbot] [jfs?] INFO: task hung in jfs_flush_journal (5) From: syzbot To: yun.zhou@windriver.com Cc: yun.zhou@windriver.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" > #syz test This crash does not have a reproducer. I cannot test it. > > On 5/2/26 04:24, syzbot wrote: >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hello, >> >> syzbot found the following issue on: >> >> HEAD commit: dca922e019dd Merge tag 'xsa48x-7.1-tag' of git://git.kerne.. >> git tree: upstream >> console output: https://syzkaller.appspot.com/x/log.txt?x=16517236580000 >> kernel config: https://syzkaller.appspot.com/x/.config?x=f2e8ebfec4636d32 >> dashboard link: https://syzkaller.appspot.com/bug?extid=139671f0b42887d37af9 >> compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8 >> >> Unfortunately, I don't have any reproducer for this issue yet. >> >> Downloadable assets: >> disk image: https://storage.googleapis.com/syzbot-assets/ccd2346f1455/disk-dca922e0.raw.xz >> vmlinux: https://storage.googleapis.com/syzbot-assets/b31792c5bbeb/vmlinux-dca922e0.xz >> kernel image: https://storage.googleapis.com/syzbot-assets/fcd62dbc97c7/bzImage-dca922e0.xz >> >> IMPORTANT: if you fix the issue, please add the following tag to the commit: >> Reported-by: syzbot+139671f0b42887d37af9@syzkaller.appspotmail.com >> >> INFO: task jfsCommit:127 blocked in I/O wait for more than 143 seconds. >> Not tainted syzkaller #0 >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> Call Trace: >> >> context_switch kernel/sched/core.c:5387 [inline] >> __schedule+0x1681/0x54c0 kernel/sched/core.c:7188 >> __schedule_loop kernel/sched/core.c:7267 [inline] >> schedule+0x164/0x360 kernel/sched/core.c:7282 >> io_schedule+0x80/0xe0 kernel/sched/core.c:8109 >> __lock_metapage fs/jfs/jfs_metapage.c:52 [inline] >> lock_metapage+0x1ff/0x400 fs/jfs/jfs_metapage.c:66 >> __get_metapage+0x49a/0xe20 fs/jfs/jfs_metapage.c:749 >> diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672 >> diFree+0x9dd/0x2ca0 fs/jfs/jfs_imap.c:959 >> jfs_evict_inode+0x331/0x440 fs/jfs/inode.c:162 >> evict+0x61e/0xb10 fs/inode.c:841 >> txLazyCommit fs/jfs/jfs_txnmgr.c:2666 [inline] >> jfs_lazycommit+0x3ef/0xa10 fs/jfs/jfs_txnmgr.c:2735 >> kthread+0x388/0x470 kernel/kthread.c:436 >> ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 >> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 >> >> INFO: task syz-executor:7027 blocked for more than 143 seconds. >> Not tainted syzkaller #0 >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. >> task:syz-executor state:D stack:21696 pid:7027 tgid:7027 ppid:1 task_flags:0x400140 flags:0x00080002 >> Call Trace: >> >> context_switch kernel/sched/core.c:5387 [inline] >> __schedule+0x1681/0x54c0 kernel/sched/core.c:7188 >> __schedule_loop kernel/sched/core.c:7267 [inline] >> schedule+0x164/0x360 kernel/sched/core.c:7282 >> jfs_flush_journal+0x721/0xf50 fs/jfs/jfs_logmgr.c:1561 >> jfs_sync_fs+0x7d/0xa0 fs/jfs/super.c:649 >> sync_filesystem+0x1ce/0x250 fs/sync.c:66 >> generic_shutdown_super+0x77/0x2d0 fs/super.c:625 >> kill_block_super+0x44/0x90 fs/super.c:1725 >> deactivate_locked_super+0xbc/0x130 fs/super.c:476 >> cleanup_mnt+0x437/0x4d0 fs/namespace.c:1312 >> task_work_run+0x1d9/0x270 kernel/task_work.c:233 >> resume_user_mode_work include/linux/resume_user_mode.h:50 [inline] >> __exit_to_user_mode_loop kernel/entry/common.c:67 [inline] >> exit_to_user_mode_loop+0xed/0x480 kernel/entry/common.c:98 >> __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline] >> syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:238 [inline] >> syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline] >> do_syscall_64+0x33e/0xf80 arch/x86/entry/syscall_64.c:100 >> entry_SYSCALL_64_after_hwframe+0x77/0x7f >> RIP: 0033:0x7fc31715e017 >> RSP: 002b:00007ffde604b778 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6 >> RAX: 0000000000000000 RBX: 00007fc3171f2120 RCX: 00007fc31715e017 >> RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffde604b830 >> RBP: 00007ffde604b830 R08: 00007ffde604c830 R09: 00000000ffffffff >> R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffde604c8c0 >> R13: 00007fc3171f2120 R14: 000000000004aab3 R15: 00007ffde604c900 >> >> >> Showing all locks held in the system: >> 2 locks held by kworker/0:0/9: >> 4 locks held by pr/legacy/17: >> 1 lock held by khungtaskd/38: >> #0: ffffffff8dfc8140 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline] >> #0: ffffffff8dfc8140 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:838 [inline] >> #0: ffffffff8dfc8140 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775 >> 2 locks held by jfsCommit/127: >> #0: ffff88803a2d0900 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x2e8/0x2ca0 fs/jfs/jfs_imap.c:889 >> #1: ffff8880620e1e60 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x306/0x2ca0 fs/jfs/jfs_imap.c:894 >> 3 locks held by kworker/u8:6/163: >> 6 locks held by kworker/u8:7/177: >> 8 locks held by kworker/u8:13/2439: >> 3 locks held by kworker/u9:1/4914: >> #0: ffff888032623938 ((wq_completion)hci4){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3277 [inline] >> #0: ffff888032623938 ((wq_completion)hci4){+.+.}-{0:0}, at: process_scheduled_works+0xa35/0x1860 kernel/workqueue.c:3385 >> #1: ffffc9001023fc40 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3278 [inline] >> #1: ffffc9001023fc40 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_scheduled_works+0xa70/0x1860 kernel/workqueue.c:3385 >> #2: ffff8880632f4f80 (&hdev->req_lock){+.+.}-{4:4}, at: hci_cmd_sync_work+0x1d3/0x400 net/bluetooth/hci_sync.c:331 >> 1 lock held by syslogd/4946: >> #0: ffff888032aef398 (&si->socket.wq.wait){+.+.}-{3:3}, at: spin_lock include/linux/spinlock_rt.h:45 [inline] >> #0: ffff888032aef398 (&si->socket.wq.wait){+.+.}-{3:3}, at: finish_wait+0xbe/0x1e0 kernel/sched/wait.c:394 >> 3 locks held by klogd/4953: >> 2 locks held by dhcpcd/5258: >> #0: ffffffff8f336db8 (vlan_ioctl_mutex){+.+.}-{4:4}, at: sock_ioctl+0x644/0x7f0 net/socket.c:1396 >> #1: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: vlan_ioctl_handler+0xf0/0x630 net/8021q/vlan.c:579 >> 2 locks held by getty/5351: >> #0: ffff888036f1d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243 >> #1: ffffc90003cbe2e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x462/0x13a0 drivers/tty/n_tty.c:2211 >> 1 lock held by syz-executor/7027: >> #0: ffff888035fb60d0 (&type->s_umount_key#62){+.+.}-{4:4}, at: __super_lock fs/super.c:58 [inline] >> #0: ffff888035fb60d0 (&type->s_umount_key#62){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:73 [inline] >> #0: ffff888035fb60d0 (&type->s_umount_key#62){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:508 >> 1 lock held by udevd/7947: >> 7 locks held by syz-executor/8388: >> #0: ffff88803789a480 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2724 [inline] >> #0: ffff88803789a480 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x22d/0xba0 fs/read_write.c:684 >> #1: ffff88804c004878 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343 >> #2: ffff888025be5c38 (kn->active#53){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline] >> #2: ffff888025be5c38 (kn->active#53){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x540 fs/kernfs/file.c:344 >> #3: ffffffff8ebcec58 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: new_device_store+0x13c/0x710 drivers/net/netdevsim/bus.c:184 >> #4: ffff88803ecef160 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:1040 [inline] >> #4: ffff88803ecef160 (&dev->mutex){....}-{4:4}, at: __device_attach+0x88/0x450 drivers/base/dd.c:1076 >> #5: ffff88803a68e310 (&devlink->lock_key#21){+.+.}-{4:4}, at: nsim_drv_probe+0xc9/0xc30 drivers/net/netdevsim/dev.c:1658 >> #6: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline] >> #6: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_dev_lock+0x257/0x2f0 net/core/dev.c:2162 >> 4 locks held by udevd/8535: >> 1 lock held by syz-executor/8870: >> #0: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline] >> #0: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_nets_lock net/core/rtnetlink.c:341 [inline] >> #0: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_newlink+0x883/0x1bb0 net/core/rtnetlink.c:4108 >> 1 lock held by syz-executor/9085: >> #0: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline] >> #0: ffffffff8f356038 (rtnl_mutex){+.+.}-{4:4}, at: inet_rtm_newaddr+0x404/0x1ad0 net/ipv4/devinet.c:978 >> 2 locks held by syz.6.393/9090: >> 2 locks held by udevadm/9099: >> 2 locks held by syz.3.395/9101: >> >> ============================================= >> >> NMI backtrace for cpu 1 >> CPU: 1 UID: 0 PID: 38 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} >> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 >> Call Trace: >> >> dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 >> nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113 >> nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62 >> trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline] >> __sys_info lib/sys_info.c:157 [inline] >> sys_info+0x135/0x170 lib/sys_info.c:165 >> check_hung_uninterruptible_tasks kernel/hung_task.c:353 [inline] >> watchdog+0xfd3/0x1030 kernel/hung_task.c:561 >> kthread+0x388/0x470 kernel/kthread.c:436 >> ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 >> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 >> >> Sending NMI from CPU 1 to CPUs 0: >> NMI backtrace for cpu 0 >> CPU: 0 UID: 0 PID: 17 Comm: pr/legacy Not tainted syzkaller #0 PREEMPT_{RT,(full)} >> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 >> RIP: 0010:io_serial_in+0x77/0xc0 drivers/tty/serial/8250/8250_port.c:401 >> Code: e8 5e 4a 90 fc 44 89 f9 d3 e3 49 83 ee 80 4c 89 f0 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 f7 e8 af 53 f7 fc 41 03 1e 89 da ec <0f> b6 c0 5b 41 5c 41 5e 41 5f e9 4a a2 eb 05 cc 44 89 f9 80 e1 07 >> RSP: 0018:ffffc900001679d0 EFLAGS: 00000202 >> RAX: 1ffffffff3362600 RBX: 00000000000003fd RCX: 0000000000000000 >> RDX: 00000000000003fd RSI: 0000000000000000 RDI: 0000000000000000 >> RBP: ffffffff99b13870 R08: 0000000000000000 R09: 0000000000000000 >> R10: dffffc0000000000 R11: ffffffff85342690 R12: dffffc0000000000 >> R13: 0000000000000000 R14: ffffffff99b135e0 R15: 0000000000000000 >> FS: 0000000000000000(0000) GS:ffff88812617c000(0000) knlGS:0000000000000000 >> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 >> CR2: 00007f5e2a43ce00 CR3: 000000006ff82000 CR4: 00000000003526f0 >> Call Trace: >> >> serial_in drivers/tty/serial/8250/8250.h:128 [inline] >> serial_lsr_in drivers/tty/serial/8250/8250.h:150 [inline] >> wait_for_lsr+0x1aa/0x2f0 drivers/tty/serial/8250/8250_port.c:1970 >> serial8250_fifo_wait_for_lsr_thre drivers/tty/serial/8250/8250_port.c:3207 [inline] >> serial8250_console_fifo_write drivers/tty/serial/8250/8250_port.c:3290 [inline] >> serial8250_console_write+0x1391/0x1b90 drivers/tty/serial/8250/8250_port.c:3357 >> console_emit_next_record kernel/printk/printk.c:3163 [inline] >> console_flush_one_record+0x68b/0xb90 kernel/printk/printk.c:3269 >> legacy_kthread_func+0x1b6/0x250 kernel/printk/printk.c:3712 >> kthread+0x388/0x470 kernel/kthread.c:436 >> ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 >> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 >> >> >> >> --- >> This report is generated by a bot. It may contain errors. >> See https://goo.gl/tpsmEJ for more information about syzbot. >> syzbot engineers can be reached at syzkaller@googlegroups.com. >> >> syzbot will keep track of this issue. See: >> https://goo.gl/tpsmEJ#status for how to communicate with syzbot. >> >> If the report is already addressed, let syzbot know by replying with: >> #syz fix: exact-commit-title >> >> If you want to overwrite report's subsystems, reply with: >> #syz set subsystems: new-subsystem >> (See the list of subsystem names on the web dashboard) >> >> If the report is a duplicate of another one, reply with: >> #syz dup: exact-subject-of-another-report >> >> If you want to undo deduplication, reply with: >> #syz undup >> >> -- >> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group. >> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com. >> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-bugs/69f50c04.170a0220.5f1b.0017.GAE%40google.com.