From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C58A4C83F1A for ; Sat, 12 Jul 2025 05:57:36 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B3D018D0003; Sat, 12 Jul 2025 01:57:35 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id AECFD8D0001; Sat, 12 Jul 2025 01:57:35 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9DBBA8D0003; Sat, 12 Jul 2025 01:57:35 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 8A3448D0001 for ; Sat, 12 Jul 2025 01:57:35 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 1957BB6D12 for ; Sat, 12 Jul 2025 05:57:35 +0000 (UTC) X-FDA: 83654555670.01.3308159 Received: from mail-io1-f77.google.com (mail-io1-f77.google.com [209.85.166.77]) by imf04.hostedemail.com (Postfix) with ESMTP id 672FD40003 for ; Sat, 12 Jul 2025 05:57:33 +0000 (UTC) Authentication-Results: imf04.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf04.hostedemail.com: domain of 3S_lxaAkbAFAAGH2s33w9s770v.y66y3wCAw9u65Bw5B.u64@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.77 as permitted sender) smtp.mailfrom=3S_lxaAkbAFAAGH2s33w9s770v.y66y3wCAw9u65Bw5B.u64@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1752299853; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding:in-reply-to: references; bh=cPNMrF484Dbfnhhp5tZ0FCQePgb0YtzJfoKVrOiLIJQ=; b=5v0lcXcfEMY5mgANjddPLnD1I+2Q+TA881QVPPGmUgczm1R2BWzCX6j5HyhoSosrlCXBoq 1Os8o1orcAX7FCnb7YvCKdWQpPjCktnGFQ728RpfyLOfBhp58iKmyYIcSig9DPpIiWrsaZ S1R2GLu6d2eeSRrZYDiJo32ltZjLR1Q= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1752299853; a=rsa-sha256; cv=none; b=NTkFyI4BZqEPjEeEk+oKYOQ77WRfHkzCeE5Z5Gmbpl95JTPSfhH4nSKZvq5XB3kdYTGeFM zLxKQ2jcWoqcg+IbGp47H0eCAZERQiaKgONMO3b8G3wPcuVUQKwSOSPVsFnuV2t5vlow/V hyk/L2fscm9S4lNVEc/hFjN3leG/XwA= ARC-Authentication-Results: i=1; imf04.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf04.hostedemail.com: domain of 3S_lxaAkbAFAAGH2s33w9s770v.y66y3wCAw9u65Bw5B.u64@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.77 as permitted sender) smtp.mailfrom=3S_lxaAkbAFAAGH2s33w9s770v.y66y3wCAw9u65Bw5B.u64@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f77.google.com with SMTP id ca18e2360f4ac-86d1218df67so296830039f.1 for ; Fri, 11 Jul 2025 22:57:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752299852; x=1752904652; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cPNMrF484Dbfnhhp5tZ0FCQePgb0YtzJfoKVrOiLIJQ=; b=RqRMVxk+3KnWlHwCXcffHLDKH3g9KLZHomMOSl4UQ0hXyYaSDid5liJc4su6t9nyA/ XOHWjELGhsJEvqa5WDjMLtwKyEwvmzco0sLXwpo4oLi9RF2d0UN7v83tI0so6jovGuuX wkaPx+pfO7nvnVKEXCYPVyCmKMs9owsxZpyWbQwG/4OBIZLx0uwwIMiGYsn2MlWiQEsq 7HTyLsXoEeMjuN9CKPPyA1RDWkOemDiXCeySzVWcD1CwlngzV1d3iOa3J60ZFLtA92xJ 07vQ92nXiCbdV86ZSlWPVivsqUO+2bGX8majwVHB5NGjU9Q5UloVDt/oilqhgZ1oK7Jf aOgg== X-Forwarded-Encrypted: i=1; AJvYcCUeyMviZVlURT2jigqcrhUyTN5halTsAkhbjqAzn2rDeIjm4YPxj5o/VQq3RzpjWSV9U5HzGvcS5A==@kvack.org X-Gm-Message-State: AOJu0YyA4nKZ01YIhB58zyIQPyL/hcQnNzyzgdjo/vm8IAb4EAJPi/Dp 9wYGjeONu1kPAAguLzKGtK90EXfC9Cyb5tW7UouM9735vkLP37JKeKFgcesSc/JP8iMkDDnUoUo 7sFFknYEjugYiQMmnExaCdRHwycRlfgjD8v9YleQGS7OExT07FEh8j1tAJ5g= X-Google-Smtp-Source: AGHT+IEhQ6Af9mYMbBsGH05ipB+JFmzOoRIUn3SWsh9RIbI5r6JbDqM8JaovKNxONp96/IxdZl/OiJT+gnDSseps0MeiuZrkxr3r MIME-Version: 1.0 X-Received: by 2002:a05:6602:6a96:b0:862:fe54:df4e with SMTP id ca18e2360f4ac-879787e2f72mr710785239f.7.1752299851965; Fri, 11 Jul 2025 22:57:31 -0700 (PDT) Date: Fri, 11 Jul 2025 22:57:31 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6871f94b.a00a0220.26a83e.0070.GAE@google.com> Subject: [syzbot] [mm?] possible deadlock in lock_next_vma From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, lorenzo.stoakes@oracle.com, shakeel.butt@linux.dev, surenb@google.com, syzkaller-bugs@googlegroups.com, vbabka@suse.cz Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 672FD40003 X-Stat-Signature: hesaa3z317mc5cfac86fb6igp4d8iygn X-Rspam-User: X-Rspamd-Server: rspam07 X-HE-Tag: 1752299853-696287 X-HE-Meta: U2FsdGVkX1/fEa15KcWytlKyAbvPPBU9b9G/mEFla9HChZdRisjX/cCz+sL1KRdy1FIXsDC8aBEdNg91rGz36YAI3V2efGh6R95PoaAuKa/q6YUsFijeMr47Xvb1RBz1J7LVic7Apf7uYtA159TiMnpdC0i4Ant24QlEOl5/CtoJvlLEmZiFm/+HNFwAH4acECJTQjpK7bJnArzJKMh5J57GTNtXAVkntzLqGa/e+b+ius4gdAmhWZPSZu7jD3JyN+RO249Yc6dMKrtUZ3eTrJqulSQWlv0XKt8qmcnJ4y6/KGfov6AKpzDVlADEnw4LnqBUh//DJKlQWPYWsi5G64V1WS5Aq0i1kj60TpIbibNbdYPolOSboD/d0KaeSgiAjs2WfHt+oZsb6lyMwg3oIpLPTsFMrBbrsH3b22E1phmxhwEngs49h6yP4SvFi7OdayQ7JQt88CmT5IjccolZFM7pdOrwpHwUWTtjH1d6oxwTUDvDwBIdPO/jGnIOWhtgO+YNd+XUUbqhDsdrOL+NaJrM2QzcsIpv8UMd3H9PGfDZuG9yeCQ4NWnZowa1Nj8s15QMxPVSsXFh/egmA5ekOjaJlx3es8aG3zP0+xhvWHEs7CQkWAM2jqSf5BXGg+JA8rUkCAFSJFItCZIumFMcW6OPv7Xsvn8r84/wsIq4CJGgs+bc41wa+2SoRcTwA2N26vW9gtf6894d3gdQUCIQ5D1yz6XZRr7/mZg1kIUasZptPiTiWuVfXxLpTL4chyF/tqGkgwEhZL1WMZki2eMOGlL2OT98aoIKrNgAnk9ioNqTCG+D2wV8h3obdVGhqxsz9pp5Q6fmQw2z/sOpkfSxifTq38MhPrmcr6LOw0VsKLVRYO0KGQFqW0BJPUwyf5V63LesCtQEomJE1lQcbq4bdG15UZyVJ7tqzG0bXR/mQcjcgdIVS2/LGU4xJqWgUzzSnzkZRLrgc88eatDuLqf +ho0zmVI XrC9XYWSf7VrRJrUpu2t9l80YIJgIUnF4+tPaJX2YsaIGRpa105G4pBUSPyOcNq6WXYBvsWj6YUmaqOoTmvZKeU0iR3k5dX8ASQ2V3LoqwtRYXDKytO+pdK++cVuXoe9QJ8kY384L4K262GsjkaNvPo1TXLpP2kmKYY5UUaOFDR99U0yCCmRb5qwFZh1AvagldZUI3me30Jq+xZCKoauEhw6i6uP6F48PayQSrUdd2Qf/RgXAmzhR3wMy60rfB5unpPMeTtSn95q3sEQ2asfrVW69p96rgs/d3A+fk/nr5qp7qPU3zNvGgL3Nj423POQPTJp4Kbg8mBwU+gqHJbH0uTXe5W241hexmU8RMXIQQG7jwo/l9N+2l5dD3ypPAsMDPBz+j2aP/5xZV6wAi3c/oANgTRyDSEgB/GbzMZ/WVhVBoMh2eQ1dFanQFkHC52Mjc8Dj2E6dnYocv65eWUf9y5qRjh36LHY4/KwPRQxbcQlWXgXsYqOBB1EFGzrjsnt3fjfJ+NnRiiMAVrRU96Ps1d/mtW0t8sv+xM27yzCyzaR6kUP8IChCB1LBWlDW7vVUMeXjCt76PnrOWg/y3/9DExHUx9BiJp6rZI8fUNR82aV1XqHQilE34QGms6QH2CqYsK9pfnnvq+Nlxe94XcFtfU+evOJ9Y+4Z7PGmh4GLlZXo7fbqGO1m3xejIeamyDnMFpiqdGCzCnGXw0fJzYrY5zG++6PE8lQy+jVSGextPYC8XyIwYejDkK3zC58th0OLpIl0GwTY3V9udtA4+XXlooU+uRZo7YatOaiC/6LpF5ADRegZtK7mnGIj+F1mULLND55+IEmSkmeDPM8ZEfht3ywik+jNyi3KEISPnWBUv6hbUyHSPQVA1zYdsVX65ivigCtkZbrWHDT29Qphuyglw6MIOPiB0ViuTiBpS29Gy6qUspoWIjCOP1SKcEBWvcynOR76SXzTqi7oqBHGY+n9KiRiJw1K tIMnB7fr TDSict24SQPqKOa5MpiWurAJpNeHK9I8B9YJsMOZ/MTc/7Zvm9UzcuPcw/Baj68Res98Ggf11kRsGkCT/sTOsB4IkAnKvtvNJpTark4wKlM7BUrKJMQOHiXHM507SmLrydb7fukduZUxipuRvL8twurUO0ULTGH2T7snFjpVeh7wTJ+wFyqMXAp9Cx7rmj51SldwSGy9pdreq6kvLn1a9rgRQbKxF3VpaYwKa5ry7GG2UNST9yf4CR1fTm6NoidQ3/1NJd4DGjqlupu2A1kyo4suSxX0v7WTTG1RDab08XWL7rOKxtjiLrja63GzHEbYq+wfkCiWyBE0x+w1XrWFzY9k/3M5aNe7yCXy2x8ZbjN8NLluRufdDS07d2JNmstxj5jYIMice9E7Q8AyqpeSWQSKIbDceU5w4xxHYBPZc672Hs1xefLLXmjpn5CvX128pZofGIzJDfvI7YNHzFLERJFZj6VOXIXJ20s3Du/EC0FThL8sbCdg50P2xIEr+N3e X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Hello, syzbot found the following issue on: HEAD commit: 26ffb3d6f02c Add linux-next specific files for 20250704 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=12d4df70580000 kernel config: https://syzkaller.appspot.com/x/.config?x=1e4f88512ae53408 dashboard link: https://syzkaller.appspot.com/bug?extid=159a3ef1894076a6a6e9 compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/fd5569903143/disk-26ffb3d6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1b0c9505c543/vmlinux-26ffb3d6.xz kernel image: https://storage.googleapis.com/syzbot-assets/9d864c72bed1/bzImage-26ffb3d6.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+159a3ef1894076a6a6e9@syzkaller.appspotmail.com ====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc4-next-20250704-syzkaller #0 Not tainted ------------------------------------------------------ syz.4.1737/14243 is trying to acquire lock: ffff88807634d1e0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock_killable include/linux/mmap_lock.h:432 [inline] ffff88807634d1e0 (&mm->mmap_lock){++++}-{4:4}, at: lock_vma_under_mmap_lock mm/mmap_lock.c:189 [inline] ffff88807634d1e0 (&mm->mmap_lock){++++}-{4:4}, at: lock_next_vma+0x802/0xdc0 mm/mmap_lock.c:264 but task is already holding lock: ffff888020b36a88 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (vm_lock){++++}-{0:0}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __vma_enter_locked+0x182/0x380 mm/mmap_lock.c:63 __vma_start_write+0x1e/0x120 mm/mmap_lock.c:87 vma_start_write include/linux/mmap_lock.h:267 [inline] mprotect_fixup+0x571/0x9b0 mm/mprotect.c:670 setup_arg_pages+0x53a/0xaa0 fs/exec.c:670 load_elf_binary+0xb9f/0x2730 fs/binfmt_elf.c:1013 search_binary_handler fs/exec.c:1670 [inline] exec_binprm fs/exec.c:1702 [inline] bprm_execve+0x99c/0x1450 fs/exec.c:1754 kernel_execve+0x8f0/0x9f0 fs/exec.c:1920 try_to_run_init_process+0x13/0x60 init/main.c:1397 kernel_init+0xad/0x1d0 init/main.c:1525 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 -> #0 (&mm->mmap_lock){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read_killable+0x50/0x350 kernel/locking/rwsem.c:1547 mmap_read_lock_killable include/linux/mmap_lock.h:432 [inline] lock_vma_under_mmap_lock mm/mmap_lock.c:189 [inline] lock_next_vma+0x802/0xdc0 mm/mmap_lock.c:264 get_next_vma fs/proc/task_mmu.c:182 [inline] query_vma_find_by_addr fs/proc/task_mmu.c:516 [inline] query_matching_vma+0x28f/0x4b0 fs/proc/task_mmu.c:545 do_procmap_query fs/proc/task_mmu.c:637 [inline] procfs_procmap_ioctl+0x406/0xce0 fs/proc/task_mmu.c:748 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(vm_lock); lock(&mm->mmap_lock); lock(vm_lock); rlock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz.4.1737/14243: #0: ffff888020b36e48 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220 #1: ffff888020b36a88 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220 stack backtrace: CPU: 1 UID: 0 PID: 14243 Comm: syz.4.1737 Not tainted 6.16.0-rc4-next-20250704-syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read_killable+0x50/0x350 kernel/locking/rwsem.c:1547 mmap_read_lock_killable include/linux/mmap_lock.h:432 [inline] lock_vma_under_mmap_lock mm/mmap_lock.c:189 [inline] lock_next_vma+0x802/0xdc0 mm/mmap_lock.c:264 get_next_vma fs/proc/task_mmu.c:182 [inline] query_vma_find_by_addr fs/proc/task_mmu.c:516 [inline] query_matching_vma+0x28f/0x4b0 fs/proc/task_mmu.c:545 do_procmap_query fs/proc/task_mmu.c:637 [inline] procfs_procmap_ioctl+0x406/0xce0 fs/proc/task_mmu.c:748 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl+0xf9/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f79bc78e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f79bd5c8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f79bc9b6080 RCX: 00007f79bc78e929 RDX: 0000200000000180 RSI: 00000000c0686611 RDI: 0000000000000006 RBP: 00007f79bc810b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f79bc9b6080 R15: 00007ffcdd82ae18 --- 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