possible deadlock in hugetlbfs_file_mmap

Status: upstream: reported on 2026/11/05 11:22
Subsystems: fs mm
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+d7d72f3d467710442af0@syzkaller.appspotmail.com
First crash: 2d03h, last: 2d03h
✨ AI-generated root cause summary:

In the Network Block Device (NBD) driver, sockets used for block transport must be reclassified to dedicated lockdep lock classes (sk_lock-AF_INET-NBD) to avoid false and real circular locking dependencies with userspace network sockets that acquire mm->mmap_lock on page faults. While nbd_add_socket() properly invokes nbd_reclassify_socket(), nbd_genl_reconnect_sock_cb() replaces dead sockets during reconnection via nbd_get_socket() without calling nbd_reclassify_socket(). As a result, the reconnected socket retains the generic sk_lock-AF_INET lock class, causing socket operations like kernel_sock_shutdown() executed under &nsock->tx_lock (e.g., in recv_work -> nbd_mark_nsock_dead) to register a dependency chain from fs_reclaim through blk-mq queue usage, elevator lock, &cmd->lock, and &nsock->tx_lock to sk_lock-AF_INET and mm->mmap_lock, producing a circular locking dependency warning.

▶ ▼ ✨ Full AI root cause analysis
Based on kernel commit c3e67bd82b9b:

Technical Root Cause Analysis

1. Components Involved

  • Source File: drivers/block/nbd.c
  • Functions:
    • nbd_genl_reconnect_sock_cb()
    • nbd_add_socket()
    • nbd_reclassify_socket()
    • nbd_mark_nsock_dead()
    • recv_work()
  • Structs & Fields:
    • struct nbd_sock: nsock->sock, nsock->tx_lock
    • struct socket / struct sock: sk->sk_lock

2. Background and Invariants

In the Linux kernel, standard userspace network sockets (such as TCP/IPv4 sockets belonging to the sk_lock-AF_INET lockdep class) establish an ordering dependency: $$\text{sk_lock-AF_INET} \longrightarrow \text{&mm->mmap_lock}$$ This occurs because data-copying operations like tcp_sendmsg_locked() hold lock_sock(sk) and invoke copy_from_iter() on user-provided buffers; if those buffers are memory-mapped, page faults trigger __might_fault(), which acquires &mm->mmap_lock.

In turn, operations holding &mm->mmap_lock (e.g., mmap() or page allocation) can trigger direct memory reclaim (fs_reclaim). Under fs_reclaim, dirty pages may be written back to swap or filesystems backed by block devices, establishing: $$\text{fs_reclaim} \longrightarrow \text{&q->q_usage_counter(io)}$$

When a block device request queue is managed by blk-mq:

  1. Freezing or updating queue scheduler configuration (blk_mq_update_nr_hw_queues(), elevator_change()) takes &q->elevator_lock under q->q_usage_counter.
  2. Quiescing queues (elevator_switch()) calls synchronize_srcu(&set->srcu) to wait for inflight request dispatch.
  3. Request dispatch invokes the block driver's .queue_rq handler (nbd_queue_rq()), which locks &cmd->lock and calls nbd_handle_cmd(), which acquires &nsock->tx_lock.

Because NBD transmits and manages network sockets under &nsock->tx_lock inside the block I/O path, acquiring a socket lock (lock_sock()) while holding &nsock->tx_lock would bridge: $$\text{&nsock->tx_lock} \longrightarrow \text{sk_lock-AF_INET}$$ thereby closing a circular locking dependency: $$\text{fs_reclaim} \longrightarrow \text{&q->q_usage_counter(io)} \longrightarrow \text{&q->elevator_lock} \longrightarrow \text{set->srcu} \longrightarrow \text{&cmd->lock} \longrightarrow \text{&nsock->tx_lock} \longrightarrow \text{sk_lock-AF_INET} \longrightarrow \text{&mm->mmap_lock} \longrightarrow \text{fs_reclaim}$$

To prevent this collision, NBD sockets must not use the generic sk_lock-AF_INET lockdep class. The driver provides nbd_reclassify_socket() (defined at lines 1245–1272 of drivers/block/nbd.c), which initializes sk->sk_lock with dedicated lock classes (sk_lock-AF_INET-NBD and slock-AF_INET-NBD).


3. Defect and Failure Mechanism

While initial socket addition in nbd_add_socket() correctly calls nbd_reclassify_socket(sock) after nbd_get_socket():

static int nbd_add_socket(struct nbd_device *nbd, unsigned long arg, bool netlink)
{
    ...
    sock = nbd_get_socket(nbd, arg, &err);
    if (!sock)
        return err;
    nbd_reclassify_socket(sock);
    ...
}

The netlink socket reconnection callback, nbd_genl_reconnect_sock_cb() (invoked via nbd_genl_reconfigure()), replaces dead sockets on a running device using nbd_get_socket(), but fails to call nbd_reclassify_socket(sock):

static int nbd_genl_reconnect_sock_cb(struct nbd_device *nbd, unsigned long arg)
{
    ...
    sock = nbd_get_socket(nbd, arg, &err);
    if (!sock)
        return err;

    args = kzalloc_obj(*args);
    ...
    nsock->sock = sock;
    ...
    INIT_WORK(&args->work, recv_work);
    queue_work(nbd->recv_workq, &args->work);
    ...
}

Because nbd_reclassify_socket() is omitted:

  1. The reconnected socket retains the generic sk_lock-AF_INET lockdep key.
  2. When an error or connection reset occurs, recv_work() acquires mutex_lock(&nsock->tx_lock) and calls nbd_mark_nsock_dead(nbd, nsock, 1).
  3. nbd_mark_nsock_dead() invokes kernel_sock_shutdown(nsock->sock, SHUT_RDWR), which calls inet_shutdown() and acquires lock_sock(sk).
  4. Lockdep records the dependency &nsock->tx_lock -> sk_lock-AF_INET.
  5. Later, when an unrelated allocation (such as resv_map_alloc() in hugetlb_reserve_pages() during hugetlbfs_file_mmap()) executes with GFP_KERNEL under &mm->mmap_lock and inode lock, lockdep traverses the graph and detects the circular lock dependency cycle, issuing the reported splat.
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
3454990c assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ FuzzingArtifact: ❌ MemoryCorruption: ❌ NetworkNeedsSetup: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ possible deadlock in hugetlbfs_file_mmap 2026/11/03 08:02 2026/11/03 08:02 2026/11/03 09:06 0a94d799
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [fs?] [mm?] possible deadlock in hugetlbfs_file_mmap 0 (1) 2026/11/05 11:22
▶ ▼ Similar bugs (1)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 possible deadlock in hugetlbfs_file_mmap origin:lts-only 4 syz, C done 242 1197d 1336d 3/3 fixed on 2023/09/28 15:44

Sample crash report:
netlink: 8 bytes leftover after parsing attributes in process `syz.2.139'.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.139/6452 is trying to acquire lock:
ffffffff90094cc0 (fs_reclaim){+.+.}-{0:0}, at: might_alloc include/linux/sched/mm.h:316 [inline]
ffffffff90094cc0 (fs_reclaim){+.+.}-{0:0}, at: slab_pre_alloc_hook mm/slub.c:4673 [inline]
ffffffff90094cc0 (fs_reclaim){+.+.}-{0:0}, at: slab_alloc_node mm/slub.c:5011 [inline]
ffffffff90094cc0 (fs_reclaim){+.+.}-{0:0}, at: __kmalloc_cache_noprof+0x61/0x600 mm/slub.c:5676

but task is already holding lock:
ffff88803e6af1b0 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
ffff88803e6af1b0 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: hugetlbfs_file_mmap+0x2de/0x630 fs/hugetlbfs/inode.c:138

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #8 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}:
       down_write+0x91/0x200 kernel/locking/rwsem.c:1631
       inode_lock include/linux/fs.h:1024 [inline]
       hugetlbfs_file_mmap+0x2de/0x630 fs/hugetlbfs/inode.c:138
       vfs_mmap include/linux/fs.h:2068 [inline]
       mmap_file mm/internal.h:256 [inline]
       __mmap_new_file_vma mm/vma.c:2623 [inline]
       __mmap_new_vma mm/vma.c:2720 [inline]
       __mmap_region mm/vma.c:3054 [inline]
       mmap_region+0x1d5e/0x2840 mm/vma.c:3136
       do_mmap+0xe0a/0x1300 mm/mmap.c:573
       vm_mmap_pgoff+0x27a/0x520 mm/util.c:581
       ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:619
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #7 (&mm->mmap_lock){++++}-{4:4}:
       __might_fault+0xcb/0x130 mm/memory.c:7530
       _copy_from_iter+0x100/0x1680 lib/iov_iter.c:271
       copy_from_iter include/linux/uio.h:236 [inline]
       copy_from_iter_full include/linux/uio.h:253 [inline]
       skb_do_copy_data_nocache include/net/sock.h:2333 [inline]
       skb_copy_to_page_nocache include/net/sock.h:2359 [inline]
       tcp_sendmsg_locked+0x214a/0x53c0 net/ipv4/tcp.c:1321
       tcp_sendmsg+0x2f/0x50 net/ipv4/tcp.c:1462
       sock_sendmsg_nosec+0x10f/0x190 net/socket.c:801
       __sock_sendmsg net/socket.c:818 [inline]
       sock_write_iter+0x2de/0x3e0 net/socket.c:1269
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x612/0xba0 fs/read_write.c:687
       ksys_write+0x150/0x270 fs/read_write.c:739
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #6 (sk_lock-AF_INET){+.+.}-{0:0}:
       lock_sock_nested+0x41/0x100 net/core/sock.c:3908
       lock_sock include/net/sock.h:1717 [inline]
       inet_shutdown+0x6a/0x390 net/ipv4/af_inet.c:911
       nbd_mark_nsock_dead+0x2cb/0x550 drivers/block/nbd.c:319
       recv_work+0x1d14/0x1e30 drivers/block/nbd.c:1030
       process_one_work kernel/workqueue.c:3495 [inline]
       process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578
       worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659
       kthread+0x38b/0x480 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

-> #5 (&nsock->tx_lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
       nbd_handle_cmd drivers/block/nbd.c:1143 [inline]
       nbd_queue_rq+0x373/0xff0 drivers/block/nbd.c:1207
       blk_mq_dispatch_rq_list+0x499/0x1990 block/blk-mq.c:2131
       __blk_mq_do_dispatch_sched block/blk-mq-sched.c:168 [inline]
       blk_mq_do_dispatch_sched block/blk-mq-sched.c:182 [inline]
       __blk_mq_sched_dispatch_requests+0xd36/0x1580 block/blk-mq-sched.c:307
       blk_mq_sched_dispatch_requests+0xd7/0x190 block/blk-mq-sched.c:329
       blk_mq_run_work_fn+0x167/0x2f0 block/blk-mq.c:2546
       process_one_work kernel/workqueue.c:3495 [inline]
       process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578
       worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659
       kthread+0x38b/0x480 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

-> #4 (&cmd->lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
       nbd_queue_rq+0xc1/0xff0 drivers/block/nbd.c:1199
       blk_mq_dispatch_rq_list+0x499/0x1990 block/blk-mq.c:2131
       __blk_mq_do_dispatch_sched block/blk-mq-sched.c:168 [inline]
       blk_mq_do_dispatch_sched block/blk-mq-sched.c:182 [inline]
       __blk_mq_sched_dispatch_requests+0xd36/0x1580 block/blk-mq-sched.c:307
       blk_mq_sched_dispatch_requests+0xd7/0x190 block/blk-mq-sched.c:329
       blk_mq_run_work_fn+0x167/0x2f0 block/blk-mq.c:2546
       process_one_work kernel/workqueue.c:3495 [inline]
       process_scheduled_works+0xc3d/0x1630 kernel/workqueue.c:3578
       worker_thread+0xa47/0xfb0 kernel/workqueue.c:3659
       kthread+0x38b/0x480 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

-> #3 (set->srcu){.+.+}-{0:0}:
       srcu_lock_sync include/linux/srcu.h:225 [inline]
       __synchronize_srcu+0xca/0x2f0 kernel/rcu/srcutree.c:1662
       elevator_switch+0x1e8/0x7b0 block/elevator.c:576
       elevator_change+0x2fa/0x480 block/elevator.c:681
       elevator_set_default+0x375/0x440 block/elevator.c:754
       blk_register_queue+0x404/0x4f0 block/blk-sysfs.c:992
       __add_disk+0x6b8/0xdb0 block/genhd.c:531
       add_disk_fwnode+0x100/0x3a0 block/genhd.c:600
       add_disk include/linux/blkdev.h:801 [inline]
       nbd_dev_add+0x733/0xb60 drivers/block/nbd.c:2026
       nbd_init+0x168/0x1f0 drivers/block/nbd.c:2743
       do_one_initcall+0x250/0x870 init/main.c:1419
       do_initcall_level+0x10a/0x1a0 init/main.c:1481
       do_initcalls+0x59/0xa0 init/main.c:1497
       kernel_init_freeable+0x29d/0x3e0 init/main.c:1732
       kernel_init+0x22/0x1d0 init/main.c:1622
       ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #2 (&q->elevator_lock){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:646 [inline]
       __mutex_lock+0x197/0x15a0 kernel/locking/mutex.c:821
       elevator_change+0x1af/0x480 block/elevator.c:679
       elevator_set_none+0xb5/0x140 block/elevator.c:769
       blk_mq_elv_switch_none block/blk-mq.c:5114 [inline]
       __blk_mq_update_nr_hw_queues block/blk-mq.c:5159 [inline]
       blk_mq_update_nr_hw_queues+0x5ef/0x19e0 block/blk-mq.c:5224
       nbd_start_device+0x189/0xb30 drivers/block/nbd.c:1530
       nbd_genl_connect+0x167d/0x1cd0 drivers/block/nbd.c:2310
       genl_family_rcv_msg_doit+0x233/0x340 net/netlink/genetlink.c:1114
       genl_family_rcv_msg net/netlink/genetlink.c:1194 [inline]
       genl_rcv_msg+0x614/0x7a0 net/netlink/genetlink.c:1209
       netlink_rcv_skb+0x226/0x4a0 net/netlink/af_netlink.c:2584
       genl_rcv+0x28/0x40 net/netlink/genetlink.c:1218
       netlink_unicast_kernel net/netlink/af_netlink.c:1335 [inline]
       netlink_unicast+0x8ef/0xa80 net/netlink/af_netlink.c:1361
       netlink_sendmsg+0x7f0/0xb20 net/netlink/af_netlink.c:1920
       sock_sendmsg_nosec+0x14e/0x190 net/socket.c:800
       __sock_sendmsg net/socket.c:818 [inline]
       ____sys_sendmsg+0x54e/0x850 net/socket.c:2715
       ___sys_sendmsg+0x2a5/0x360 net/socket.c:2769
       __sys_sendmsg net/socket.c:2801 [inline]
       __do_sys_sendmsg net/socket.c:2806 [inline]
       __se_sys_sendmsg net/socket.c:2804 [inline]
       __x64_sys_sendmsg+0x1b1/0x290 net/socket.c:2804
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&q->q_usage_counter(io)#49){++++}-{0:0}:
       blk_alloc_queue+0x544/0x690 block/blk-core.c:505
       blk_mq_alloc_queue block/blk-mq.c:4439 [inline]
       __blk_mq_alloc_disk+0x194/0x390 block/blk-mq.c:4486
       nbd_dev_add+0x494/0xb60 drivers/block/nbd.c:1996
       nbd_init+0x168/0x1f0 drivers/block/nbd.c:2743
       do_one_initcall+0x250/0x870 init/main.c:1419
       do_initcall_level+0x10a/0x1a0 init/main.c:1481
       do_initcalls+0x59/0xa0 init/main.c:1497
       kernel_init_freeable+0x29d/0x3e0 init/main.c:1732
       kernel_init+0x22/0x1d0 init/main.c:1622
       ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
       ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

-> #0 (fs_reclaim){+.+.}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3209 [inline]
       check_prevs_add kernel/locking/lockdep.c:3328 [inline]
       validate_chain kernel/locking/lockdep.c:3952 [inline]
       __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
       lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
       __fs_reclaim_acquire mm/page_alloc.c:4360 [inline]
       fs_reclaim_acquire+0x71/0x100 mm/page_alloc.c:4374
       might_alloc include/linux/sched/mm.h:316 [inline]
       slab_pre_alloc_hook mm/slub.c:4673 [inline]
       slab_alloc_node mm/slub.c:5011 [inline]
       __kmalloc_cache_noprof+0x61/0x600 mm/slub.c:5676
       _kmalloc_noprof include/linux/slab.h:991 [inline]
       resv_map_alloc+0x51/0x2c0 mm/hugetlb.c:1096
       hugetlb_reserve_pages+0x36d/0x1160 mm/hugetlb.c:6813
       hugetlbfs_file_mmap+0x475/0x630 fs/hugetlbfs/inode.c:152
       vfs_mmap include/linux/fs.h:2068 [inline]
       mmap_file mm/internal.h:256 [inline]
       __mmap_new_file_vma mm/vma.c:2623 [inline]
       __mmap_new_vma mm/vma.c:2720 [inline]
       __mmap_region mm/vma.c:3054 [inline]
       mmap_region+0x1d5e/0x2840 mm/vma.c:3136
       do_mmap+0xe0a/0x1300 mm/mmap.c:573
       vm_mmap_pgoff+0x27a/0x520 mm/util.c:581
       ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:619
       do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
       do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  fs_reclaim --> &mm->mmap_lock --> &sb->s_type->i_mutex_key#24

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sb->s_type->i_mutex_key#24);
                               lock(&mm->mmap_lock);
                               lock(&sb->s_type->i_mutex_key#24);
  lock(fs_reclaim);

 *** DEADLOCK ***

locks held by syz.2.139/6452: 2, last CPU#1:
 #0: ffff8880375bccc0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:550 [inline]
 #0: ffff8880375bccc0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1ed/0x520 mm/util.c:579
 #1: ffff88803e6af1b0 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline]
 #1: ffff88803e6af1b0 (&sb->s_type->i_mutex_key#24){+.+.}-{4:4}, at: hugetlbfs_file_mmap+0x2de/0x630 fs/hugetlbfs/inode.c:138

stack backtrace:
CPU: 1 UID: 0 PID: 6452 Comm: syz.2.139 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2087
 check_noncircular+0x12f/0x150 kernel/locking/lockdep.c:2219
 check_prev_add kernel/locking/lockdep.c:3209 [inline]
 check_prevs_add kernel/locking/lockdep.c:3328 [inline]
 validate_chain kernel/locking/lockdep.c:3952 [inline]
 __lock_acquire+0x164c/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 __fs_reclaim_acquire mm/page_alloc.c:4360 [inline]
 fs_reclaim_acquire+0x71/0x100 mm/page_alloc.c:4374
 might_alloc include/linux/sched/mm.h:316 [inline]
 slab_pre_alloc_hook mm/slub.c:4673 [inline]
 slab_alloc_node mm/slub.c:5011 [inline]
 __kmalloc_cache_noprof+0x61/0x600 mm/slub.c:5676
 _kmalloc_noprof include/linux/slab.h:991 [inline]
 resv_map_alloc+0x51/0x2c0 mm/hugetlb.c:1096
 hugetlb_reserve_pages+0x36d/0x1160 mm/hugetlb.c:6813
 hugetlbfs_file_mmap+0x475/0x630 fs/hugetlbfs/inode.c:152
 vfs_mmap include/linux/fs.h:2068 [inline]
 mmap_file mm/internal.h:256 [inline]
 __mmap_new_file_vma mm/vma.c:2623 [inline]
 __mmap_new_vma mm/vma.c:2720 [inline]
 __mmap_region mm/vma.c:3054 [inline]
 mmap_region+0x1d5e/0x2840 mm/vma.c:3136
 do_mmap+0xe0a/0x1300 mm/mmap.c:573
 vm_mmap_pgoff+0x27a/0x520 mm/util.c:581
 ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:619
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f14e739fb19
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f14e8278028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f14e7625fa0 RCX: 00007f14e739fb19
RDX: 0000000000000000 RSI: 0000000001400000 RDI: 0000200000000000
RBP: 00007f14e7437b70 R08: ffffffffffffffff R09: 0000000000000000
R10: 00000000000c3072 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f14e7626038 R14: 00007f14e7625fa0 R15: 00007ffebda95258
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/03 08:02 net c3e67bd82b9b 0a94d799 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-net-this-kasan-gce possible deadlock in hugetlbfs_file_mmap
* Struck through repros no longer work on HEAD.