From: syzbot <syzbot+b568ba42c85a332a88ee@syzkaller.appspotmail.com>
To: Dai.Ngo@oracle.com, cel@kernel.org, chuck.lever@oracle.com,
dai.ngo@oracle.com, harri@afaics.de, jlayton@kernel.org,
kolga@netapp.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org, neil@brown.name, neilb@suse.de,
okorniev@redhat.com, syzkaller-bugs@googlegroups.com,
tom@talpey.com
Subject: Re: [syzbot] [nfs?] INFO: task hung in nfsd_umount
Date: Sun, 16 Aug 2026 03:14:47 -0700 [thread overview]
Message-ID: <6a818d97.9ebadd4d.20b15e.0015.GAE@google.com> (raw)
In-Reply-To: <000000000000f8ed54061ca0d9a5@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 3eb40771c00a Merge tag 'soc-fixes-7.2-3' of git://git.kern..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1309ba79580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1d67342c314f228d
dashboard link: https://syzkaller.appspot.com/bug?extid=b568ba42c85a332a88ee
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156daa25580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ad9a79580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/21569197c3cb/disk-3eb40771.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/09af5299a851/vmlinux-3eb40771.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c657b46695b7/bzImage-3eb40771.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b568ba42c85a332a88ee@syzkaller.appspotmail.com
INFO: task syz-executor347:5620 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor347 state:D stack:22184 pid:5620 tgid:5620 ppid:5617 task_flags:0x400140 flags:0x00080001
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5510 [inline]
__schedule+0x125c/0x6730 kernel/sched/core.c:7234
__schedule_loop kernel/sched/core.c:7311 [inline]
schedule+0xdd/0x2c0 kernel/sched/core.c:7326
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7383
__mutex_lock_common kernel/locking/mutex.c:726 [inline]
__mutex_lock+0xccc/0x1bd0 kernel/locking/mutex.c:821
nfsd_shutdown_threads+0x5b/0xf0 fs/nfsd/nfssvc.c:576
nfsd_umount+0x3b/0x60 fs/nfsd/nfsctl.c:1365
deactivate_locked_super+0xc1/0x1b0 fs/super.c:477
deactivate_super fs/super.c:510 [inline]
deactivate_super+0xe7/0x110 fs/super.c:506
cleanup_mnt+0x21f/0x450 fs/namespace.c:1317
task_work_run+0x150/0x240 kernel/task_work.c:233
ptrace_notify+0xf3/0x120 kernel/signal.c:2531
ptrace_report_syscall include/linux/ptrace.h:416 [inline]
ptrace_report_syscall_exit include/linux/ptrace.h:478 [inline]
arch_ptrace_report_syscall_exit include/linux/entry-common.h:213 [inline]
syscall_exit_work include/linux/entry-common.h:248 [inline]
syscall_exit_to_user_mode_work include/linux/entry-common.h:279 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:316 [inline]
do_syscall_64+0x6c0/0x870 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f056f6eec17
RSP: 002b:00007ffff209c618 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 000000000001399c RCX: 00007f056f6eec17
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffff209c6d0
RBP: 00007ffff209c6d0 R08: 00007ffff209d6d0 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000206 R12: 00007ffff209d740
R13: 0000555587301780 R14: 00007ffff209d740 R15: 0000000000000001
</TASK>
INFO: task syz-executor347:5775 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor347 state:D stack:27448 pid:5775 tgid:5775 ppid:5618 task_flags:0x400140 flags:0x00080002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5510 [inline]
__schedule+0x125c/0x6730 kernel/sched/core.c:7234
__schedule_loop kernel/sched/core.c:7311 [inline]
schedule+0xdd/0x2c0 kernel/sched/core.c:7326
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7383
__mutex_lock_common kernel/locking/mutex.c:726 [inline]
__mutex_lock+0xccc/0x1bd0 kernel/locking/mutex.c:821
write_ports+0xa5/0xcc0 fs/nfsd/nfsctl.c:860
nfsctl_transaction_write+0x106/0x1a0 fs/nfsd/nfsctl.c:112
vfs_write+0x2aa/0x1050 fs/read_write.c:685
ksys_write+0x12a/0x250 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f056f6eea19
RSP: 002b:00007ffff209d708 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 645f6473666e2f2e RCX: 00007f056f6eea19
RDX: 0000000000000005 RSI: 0000200000000700 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007f056f75a222 R09: 00007f056f75a222
R10: 00007f056f75a222 R11: 0000000000000246 R12: 00007f056f75a47b
R13: 0000000000000001 R14: 00007ffff209d740 R15: 0000000000000000
</TASK>
INFO: task syz-executor347:5776 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor347 state:D stack:27088 pid:5776 tgid:5776 ppid:5615 task_flags:0x400140 flags:0x00080002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5510 [inline]
__schedule+0x125c/0x6730 kernel/sched/core.c:7234
__schedule_loop kernel/sched/core.c:7311 [inline]
schedule+0xdd/0x2c0 kernel/sched/core.c:7326
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7383
__mutex_lock_common kernel/locking/mutex.c:726 [inline]
__mutex_lock+0xccc/0x1bd0 kernel/locking/mutex.c:821
write_ports+0xa5/0xcc0 fs/nfsd/nfsctl.c:860
nfsctl_transaction_write+0x106/0x1a0 fs/nfsd/nfsctl.c:112
vfs_write+0x2aa/0x1050 fs/read_write.c:685
ksys_write+0x12a/0x250 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f056f6eea19
RSP: 002b:00007ffff209d708 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 645f6473666e2f2e RCX: 00007f056f6eea19
RDX: 0000000000000005 RSI: 0000200000000700 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007f056f75a222 R09: 00007f056f75a222
R10: 00007f056f75a222 R11: 0000000000000246 R12: 00007f056f75a47b
R13: 0000000000000001 R14: 00007ffff209d740 R15: 0000000000000000
</TASK>
INFO: task syz-executor347:5777 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor347 state:D stack:27848 pid:5777 tgid:5777 ppid:5614 task_flags:0x400140 flags:0x00080002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5510 [inline]
__schedule+0x125c/0x6730 kernel/sched/core.c:7234
__schedule_loop kernel/sched/core.c:7311 [inline]
schedule+0xdd/0x2c0 kernel/sched/core.c:7326
schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:7383
__mutex_lock_common kernel/locking/mutex.c:726 [inline]
__mutex_lock+0xccc/0x1bd0 kernel/locking/mutex.c:821
write_ports+0xa5/0xcc0 fs/nfsd/nfsctl.c:860
nfsctl_transaction_write+0x106/0x1a0 fs/nfsd/nfsctl.c:112
vfs_write+0x2aa/0x1050 fs/read_write.c:685
ksys_write+0x12a/0x250 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x870 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f056f6eea19
RSP: 002b:00007ffff209d708 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 645f6473666e2f2e RCX: 00007f056f6eea19
RDX: 0000000000000005 RSI: 0000200000000700 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007f056f75a222 R09: 00007f056f75a222
R10: 00007f056f75a222 R11: 0000000000000246 R12: 00007f056f75a47b
R13: 0000000000000001 R14: 00007ffff209d740 R15: 0000000000000000
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/31:
#0: ffffffff8ede8200 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:300 [inline]
#0: ffffffff8ede8200 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:840 [inline]
#0: ffffffff8ede8200 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x3d/0x184 kernel/locking/lockdep.c:6775
5 locks held by kworker/u8:6/152:
2 locks held by getty/5348:
#0: ffff888037c7d0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x24/0x80 drivers/tty/tty_ldisc.c:243
#1: ffffc900032332e8 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x419/0x14e0 drivers/tty/n_tty.c:2211
2 locks held by syz-executor347/5619:
#0: ffff88806d1b80d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: __super_lock fs/super.c:58 [inline]
#0: ffff88806d1b80d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:73 [inline]
#0: ffff88806d1b80d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: deactivate_super fs/super.c:509 [inline]
#0: ffff88806d1b80d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: deactivate_super+0xdf/0x110 fs/super.c:506
#1: ffffffff8f272480 (nfsd_mutex){+.+.}-{4:4}, at: nfsd_shutdown_threads+0x5b/0xf0 fs/nfsd/nfssvc.c:576
2 locks held by syz-executor347/5620:
#0: ffff88806d2220d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: __super_lock fs/super.c:58 [inline]
#0: ffff88806d2220d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:73 [inline]
#0: ffff88806d2220d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: deactivate_super fs/super.c:509 [inline]
#0: ffff88806d2220d8 (&type->s_umount_key#67){+.+.}-{4:4}, at: deactivate_super+0xdf/0x110 fs/super.c:506
#1: ffffffff8f272480 (nfsd_mutex){+.+.}-{4:4}, at: nfsd_shutdown_threads+0x5b/0xf0 fs/nfsd/nfssvc.c:576
2 locks held by syz-executor347/5775:
#0: ffff888079e4c450 (sb_writers#9){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:739
#1: ffffffff8f272480 (nfsd_mutex){+.+.}-{4:4}, at: write_ports+0xa5/0xcc0 fs/nfsd/nfsctl.c:860
2 locks held by syz-executor347/5776:
#0: ffff88807af5e450 (sb_writers#9){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:739
#1: ffffffff8f272480 (nfsd_mutex){+.+.}-{4:4}, at: write_ports+0xa5/0xcc0 fs/nfsd/nfsctl.c:860
2 locks held by syz-executor347/5777:
#0: ffff8880246f6450 (sb_writers#9){.+.+}-{0:0}, at: ksys_write+0x12a/0x250 fs/read_write.c:739
#1: ffffffff8f272480 (nfsd_mutex){+.+.}-{4:4}, at: write_ports+0xa5/0xcc0 fs/nfsd/nfsctl.c:860
=============================================
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 07/16/2026
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
nmi_cpu_backtrace.cold+0x12d/0x151 lib/nmi_backtrace.c:122
nmi_trigger_cpumask_backtrace+0x21c/0x2a0 lib/nmi_backtrace.c:65
trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
__sys_info lib/sys_info.c:157 [inline]
sys_info+0x141/0x190 lib/sys_info.c:165
check_hung_uninterruptible_tasks kernel/hung_task.c:353 [inline]
watchdog+0xcb1/0x1030 kernel/hung_task.c:561
kthread+0x370/0x450 kernel/kthread.c:436
ret_from_fork+0x72b/0xd50 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: 13 Comm: kworker/u8:1 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/2026
Workqueue: bat_events batadv_mcast_mla_update
RIP: 0010:_static_cpu_has arch/x86/include/asm/cpufeature.h:101 [inline]
RIP: 0010:addr_has_metadata mm/kasan/kasan.h:334 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:188 [inline]
RIP: 0010:kasan_check_range+0x31/0x1e0 mm/kasan/generic.c:200
Code: 0f 84 7a 01 00 00 48 89 f8 41 54 41 89 d0 48 01 f0 55 53 0f 82 e6 00 00 00 eb 0f cc cc cc 48 b8 00 00 00 00 00 00 00 ff eb 0a <48> b8 00 00 00 00 00 80 ff ff 48 39 c7 0f 82 c2 00 00 00 4c 8d 54
RSP: 0018:ffffc90000127a60 EFLAGS: 00000282
RAX: ffffc90000127b34 RBX: ffffc90000127b30 RCX: ffffffff8b8815dd
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc90000127b30
RBP: 0000000000000004 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff88807832d8a8 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff888123cde000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005620a0b86660 CR3: 000000000eb94000 CR4: 00000000003526f0
Call Trace:
<TASK>
__asan_memset+0x23/0x50 mm/kasan/shadow.c:84
batadv_mcast_mla_flags_get net/batman-adv/multicast.c:283 [inline]
__batadv_mcast_mla_update net/batman-adv/multicast.c:907 [inline]
batadv_mcast_mla_update+0x10d/0x3200 net/batman-adv/multicast.c:946
process_one_work+0xa23/0x1940 kernel/workqueue.c:3322
process_scheduled_works kernel/workqueue.c:3405 [inline]
worker_thread+0x5ef/0xe50 kernel/workqueue.c:3486
kthread+0x370/0x450 kernel/kthread.c:436
ret_from_fork+0x72b/0xd50 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
prev parent reply other threads:[~2026-08-16 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 4:37 [syzbot] [nfs?] INFO: task hung in nfsd_umount syzbot
2024-07-07 10:49 ` Jeff Layton
2024-07-08 0:07 ` NeilBrown
2024-09-21 7:58 ` Harald Dunkel
2024-09-28 7:41 ` Harald Dunkel
2024-09-28 22:23 ` NeilBrown
2024-09-29 8:23 ` Harald Dunkel
2024-09-29 9:59 ` NeilBrown
2024-10-01 10:21 ` Harald Dunkel
2024-10-02 13:55 ` Harald Dunkel
2024-10-02 14:06 ` Harald Dunkel
2024-10-04 12:21 ` Harald Dunkel
2024-10-04 23:37 ` NeilBrown
2024-10-07 10:51 ` Harald Dunkel
2024-10-07 18:54 ` Harald Dunkel
2026-08-16 10:14 ` syzbot [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a818d97.9ebadd4d.20b15e.0015.GAE@google.com \
--to=syzbot+b568ba42c85a332a88ee@syzkaller.appspotmail.com \
--cc=Dai.Ngo@oracle.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=harri@afaics.de \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom@talpey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.