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 89FB3C83F17 for ; Mon, 14 Jul 2025 16:38:37 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0147A6B0092; Mon, 14 Jul 2025 12:38:37 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id F07A56B00A9; Mon, 14 Jul 2025 12:38:36 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DF5F46B00AB; Mon, 14 Jul 2025 12:38:36 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id C5FBE6B0092 for ; Mon, 14 Jul 2025 12:38:36 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 51C83578C5 for ; Mon, 14 Jul 2025 16:38:36 +0000 (UTC) X-FDA: 83663428632.12.7E5BF59 Received: from mail-io1-f77.google.com (mail-io1-f77.google.com [209.85.166.77]) by imf30.hostedemail.com (Postfix) with ESMTP id 8036B8000F for ; Mon, 14 Jul 2025 16:38:34 +0000 (UTC) Authentication-Results: imf30.hostedemail.com; dkim=none; spf=pass (imf30.hostedemail.com: domain of 3iTJ1aAkbAA46CDyozzs5o33wr.u22uzs86s5q217s17.q20@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.77 as permitted sender) smtp.mailfrom=3iTJ1aAkbAA46CDyozzs5o33wr.u22uzs86s5q217s17.q20@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1752511114; 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:in-reply-to:references; bh=8vECSHC5HZApOKK3p2sozzKgFWuRc6UShB6Spwxs7Ok=; b=fscQMQ+d89ES1Qzv0+HnjKZi9RfPct5qQnod3X6UXsjX81rfUheGbLrgv4Sr1fYA3/GVrC Fk10kNd/C5VW0K1Li7XmfmrSac3SDX5AmY3dH1z5KKXSY9SDZp1FK738FPfOnJhvvuaYb8 WegAmw5J6AlLB+aS6z7CTD2R2eABZ2k= ARC-Authentication-Results: i=1; imf30.hostedemail.com; dkim=none; spf=pass (imf30.hostedemail.com: domain of 3iTJ1aAkbAA46CDyozzs5o33wr.u22uzs86s5q217s17.q20@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.77 as permitted sender) smtp.mailfrom=3iTJ1aAkbAA46CDyozzs5o33wr.u22uzs86s5q217s17.q20@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none) ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1752511114; a=rsa-sha256; cv=none; b=TeJazFKNjA3ytz1xLxFwE6yVDXxGgm3bqP6iRpNB12f2S5prL15ytoI8fECn79ifcSnSPR 1zjgZ21TKpi5t2qq2ndRoLXiWdOFhNEJ5wb2/FQw2qc+N//d1ZEtlSpN/mevIL/7scV/tz 4Px/XauTGZcelRGLewQc+iIn18Sbx8s= Received: by mail-io1-f77.google.com with SMTP id ca18e2360f4ac-869e9667f58so1041140439f.3 for ; Mon, 14 Jul 2025 09:38:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752511113; x=1753115913; h=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=8vECSHC5HZApOKK3p2sozzKgFWuRc6UShB6Spwxs7Ok=; b=OM8Tzv1QAb1lhKrySbpzOjIs1z0V5/nFxA7kFmnASrjTnuJJBIMI1oiGeDt6NiaZv1 rgC0xRb3yDfiarHcU+C2u5g6zr21P2VAiE0ya3ZJ9ZVOKk4BMxeSoHoAZVLAoas9MqVm gupZJdfzvnTyS0rZIeVwGuVPB6yJBAGwwa8LUNWTIfvomfCLotNHLyV4CSL3wU7142T2 7seetPeocsXu+c5OYIOx4oXAIil8x8sG0kmrZEQDCJOTqVRFCqGpXlYaX//020ZqA8g6 FmIZMk56S6QR7EJ+qgYK3PdnyrsnLxdRLJMR5VwW+KxwFyRSfYAMp6DykMDSyKvtuCRX u0QA== X-Forwarded-Encrypted: i=1; AJvYcCXTjg5sW/9nYdgGB3yRENcOw/woGpIilOHbNbZdgippUf8YfjGLzstwMVhrS8H0v8qxwv26i7AaSA==@kvack.org X-Gm-Message-State: AOJu0YxoBtxanXuXMz1JkE8taIFjTUPPOxl6ZIYn8Mo1XmVebBKBfcZe EfPYaUpkB8y0eNazCw2PAiJxof+NKyE2XvjiYmq7cnQsoJR0IbZjoI4qACUj+fMBpXcZapZ2MPA VzI/XIYZ20c2ImnH8MCyxaGlluakhKE41axmFxl7ZwYeQHETDNUmeDVpWuvA= X-Google-Smtp-Source: AGHT+IGxv3OKeAhsNMGG3ZcxHHqsJgQMLneAUR/N4UE0K0dxGV3pqhz/YTgQNtSoCHuX7519tj9SUygrQSglFclpzxXQ6Y1SP5Qt MIME-Version: 1.0 X-Received: by 2002:a05:6602:6b0d:b0:876:8bf2:e4d2 with SMTP id ca18e2360f4ac-879787a2806mr1578319039f.2.1752511113633; Mon, 14 Jul 2025 09:38:33 -0700 (PDT) Date: Mon, 14 Jul 2025 09:38:33 -0700 In-Reply-To: <6871f94b.a00a0220.26a83e.0070.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <68753289.a70a0220.18f9d4.0003.GAE@google.com> Subject: Re: [syzbot] [mm?] possible deadlock in lock_next_vma From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, liam.howlett@oracle.com, 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-Rspam-User: X-Rspamd-Queue-Id: 8036B8000F X-Rspamd-Server: rspam06 X-Stat-Signature: qowgetqe83sdapyxik3na5troo8zbf49 X-HE-Tag: 1752511114-379872 X-HE-Meta: U2FsdGVkX1+63QKFJdP+yIKZREkNPVfIKtgFH3AEOV5ZaVA5A/dx4lKHh450zSBk9IDIUZu+YK1wjrnkqEC52ZUFveuqyc8GitAgX/z2yxxfOrQDo2PXPzOpJ2Z1vueUpPPI8XXz00g6aCv2Gjlvpy/QmSfYzlQCRldd8PjYqMlwR96yNi6xGPoSaN/1XuXzm7TMuqRDC0wWMhDuURRB8IdEwFfPZD4csgOOZ9NLekDKwN+7IgO6WH8dQLI6TJxUUixEGLpT9v9iC9LyPHYFHvvGUTW/dSGDI3U16AzqHp7e83SHuazZKs1Tf/ygBkzD+p/2iSvWVqhuaqicE8pv3nnRFaOqsfuT5EP+zT/BhEDmUKze/yU3h7kdjOTu+qMZSkb1BdWFQlhoG13s99QpCvuPgJoZ19KVOD6YiJjsr7CUE2xEwC/7r7V1rHEN/T+uYACeIvvnVTf0gQz/pFHiiObdo9fx1/14r+KYVKUaUTaRPnVjqiCQXl5N2NEuPGrxC6tntfYcR/qqcZn8rPvco5glT6ySMBOeoAVvaFnvxRzhP6x450R3568EdawLfhvNU3DtIxBYhVGuLJBXTuV45mXiYiemVyFXMCsvuLqxZ8QMlXDddQu5+dIj3qFyuvUy6y3NZwdrJaQoLUb6nRN3oPdJh99kfkmvhwwZ+nHYEPHDYF7y7nILViQ5WzxC85mabAHZNthLcsvt/QNOaLhFy3C7vl1dHgVQpOAOPwVGrtaqk3e+tjFwPlS6z6TbSivOKkSLMG6T16YEGoeUeTEZX8UOnzHA+EJ1hkJog5gcfwQZrG5NVDRl9tvltbzORRmp8HgUgHnGb//jDmH6RBZpoPhx9euZa4e8VpCUUFjNyzfNPz2l8Hz3bOsYSSsAlKLoTMZjJToIhMNLbKtpi7P8P59I9uV2T8cw93vsouC25gAfIXtbJSJJSIU0JwEEz4WR3LhFPUAHWgbnXG09jut s4F23jbM uLbrJyv94B5lIKphr3XAAhTvrGluYy27JGFwr8ZlMH/OGcmoFMKF5WmYLGUA1ex1+mNxYqvPdD8xULaRoAJOpiid6dMcXivKPCEUYrJRT8dPlCQI6uwjXrSZS00SOdTYWtGNAilsa/csGnwD51dqhm5SpjE/EDs6Ljme+cg0ugVhzOEPoAkpEOEwcRdWPiA/eNnaalW38nt5PhQE6S6UE2d068sHxrPvK2HzuTAwNWbKtUyu3WU9sC8/s7dh65nhm/J6wiZul37wl+Ti17ClsrEMhjgN6Kp+3RnJ3fezEKfjv8WKRE8vxN1QQ86alGNCTVUJ35uPZSOq9+Ec/CoVc+Z90GuvWX2dlm6ltr2YZeBOdzs7w5nwMFkqeBRirLyLNTAgiDRX8K60HYbt38hkNw1C9M7z7BROx5MNg3dBPZCY2tSfY9Uzh5TUFT9Aanm5gvyFV2wDBU+4KG02TfhSt/4pvCKH1LSFRUYcMuP6L/TZVtyVUupj7vrxrKV2/HR+czPqPwZe/MRCBZ7Lt1qja/HciTeTUnAaco/tVv2ZDH7IjwhB0rmyidKNifqQSkLuZJm3KXp5tpeDl+n3rRHm6Bh8UQCgGkMQCTwi30cdC/TGiOmVyYxXupK8hiq7Q6Pyxop84eYkcA7zNet8vca6JnLHJXU2bY6SSubmZILbyNKVSlnTH2UMgTPxNt+GnNYrJpodSSnr7fvee3ypsi37bwU5FzXQAT8W7fl43DmSDzG7c/uLcHqymrjQeQv83/Nm73hi3BU3a65UQZmHSMj5+9oalfr1StUfN8Qk4FROtStju0SaRJC0Ou3UHIlln96CtziY+/DlQL1hgWmCH/YiyogNULenwu3oX/8jFDBahX7kmaJorKKMBlyZbdz+5EQ3qc0OvwFtrhInEPd0Pg8AXsZfSPwjSdx3TgMDDrFEMY9Q650fJ97tUn8VaVxdOUAQRA1C/il4JRxGATsWjY+a1/2qMeP0C Zt3+0Wxz 3CoBhV3+j7a1ATc39Es8lKH4No7JwrU9I4ixnZTgc2cou5Q1QpW5/C3Qy8gOCJtwB4bgbHONzuLGoGhAhSgD5J3v7o6W7a1hpnSgGrBQkrUS2zyKP0zjm2eSYE5Fwb/WuHMDqM7hCDcDQ5ujnFGnSqvQqDCswVXEl0tR3RuXgeQAr+C7+izJmxZ7Oc0YH1rETiqeq6+Dnrq30XraMxOrhcvUsHMXCbygmLx7V7nuimVMSKSC18hvVWkPwxX7RqCt 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: syzbot has found a reproducer for the following issue on: HEAD commit: 0be23810e32e Add linux-next specific files for 20250714 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=15cfb0f0580000 kernel config: https://syzkaller.appspot.com/x/.config?x=be9e2082003f81ff 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 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1003b18c580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11437d82580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/69e6cc49d526/disk-0be23810.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/71d1bab88eaa/vmlinux-0be23810.xz kernel image: https://storage.googleapis.com/syzbot-assets/5a516dc7bb0d/bzImage-0be23810.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-rc6-next-20250714-syzkaller #0 Not tainted ------------------------------------------------------ syz.2.103/6308 is trying to acquire lock: ffff88807d33bde0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock_killable include/linux/mmap_lock.h:432 [inline] ffff88807d33bde0 (&mm->mmap_lock){++++}-{4:4}, at: lock_vma_under_mmap_lock mm/mmap_lock.c:189 [inline] ffff88807d33bde0 (&mm->mmap_lock){++++}-{4:4}, at: lock_next_vma+0x802/0xdc0 mm/mmap_lock.c:264 but task is already holding lock: ffff8880338c6948 (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+0x999/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+0x3f9/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:1562 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:512 [inline] query_matching_vma+0x319/0x5c0 fs/proc/task_mmu.c:544 do_procmap_query fs/proc/task_mmu.c:629 [inline] procfs_procmap_ioctl+0x3f9/0xd50 fs/proc/task_mmu.c:747 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl+0xfc/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 *** 1 lock held by syz.2.103/6308: #0: ffff8880338c6948 (vm_lock){++++}-{0:0}, at: lock_next_vma+0x146/0xdc0 mm/mmap_lock.c:220 stack backtrace: CPU: 0 UID: 0 PID: 6308 Comm: syz.2.103 Not tainted 6.16.0-rc6-next-20250714-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:1562 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:512 [inline] query_matching_vma+0x319/0x5c0 fs/proc/task_mmu.c:544 do_procmap_query fs/proc/task_mmu.c:629 [inline] procfs_procmap_ioctl+0x3f9/0xd50 fs/proc/task_mmu.c:747 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl+0xfc/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:0x7fa51ab8e929 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:00007fa51b99b038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fa51adb5fa0 RCX: 00007fa51ab8e929 RDX: 0000200000000180 RSI: 00000000c0686611 RDI: 0000000000000003 RBP: 00007fa51ac10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fa51adb5fa0 R15: 00007ffdecbd3a88 --- 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.