From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f198.google.com (mail-oi1-f198.google.com [209.85.167.198]) (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 E18AD355F43 for ; Sat, 18 Jul 2026 19:05:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.198 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784401536; cv=none; b=CA3jvxKD8RVN7dZGHAEmmSMpW7iRp4VCKDcWckpc+eY7mjjfPFmS/x+DZ/BJCzjM96GBUlmQ3OEybNgk3LvFeVJEr3eUs41PzYIa67nJ64oLOkzmV71qjeSkCIkN1jXMnwacvIy1PkvnHnTUtxu2s17eSiKZDQTbvQ5FumZ3lXc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784401536; c=relaxed/simple; bh=5dv0sBuJ0LRr+o7vcIDidVKdTkPLs3w0AcVJvmcR2B4=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To:Cc: Content-Type; b=dXOROffVPTQJu+BzA74wXskTNqvh6mZo3auYEyDhkygKm+saG/kta5QDkx5db+p6x5VcYJ+As4EFZ70a2hcbKl5xQ+FSoxX50SsBO3Ga3GlXqhcfIw3D92yGxZssQfx5IIpLbkWn7kfngZxdAk7bhcqFq6yZ9tltBhVRO3OEIf8= 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.167.198 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-oi1-f198.google.com with SMTP id 5614622812f47-4a42c572645so8266757b6e.0 for ; Sat, 18 Jul 2026 12:05:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1784401528; x=1785006328; h=content-type: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:content-type; bh=0vmcegl3OOLgh38fBpJ4SPH/8D39XCHqiqIL39qmmnE=; b=Emjfwvkj7KmxPbJeORCeoLzOQkdvyUSJAD51y9B3aLGX2c2cX+mtsjl0dJ+iszuU0C NaWPv+7QieBD0vY5g8bvjGN0OzLgMKoX/nwB2wUtRLBYDbdIksl+CfmgxXtOMG8DRyrX pBcAs2bUgJC+gxy9hahfdu/q63dOqmTr/gGLo/TJFoqnS0R1tEuFOaift/91B0WwLWl7 RFTtmhfRBn5M5bMEA8I01FCn1pmjPfS/84yKykx2bp2pXOrKXywCbHLhWOXb1cd2klFb Lg1mTsCH703ept4wOGikwwPmBlpPp2XUiQDhJNvRJVztba/hoR4n6eUJiANUzadzL8n6 pKdQ== X-Gm-Message-State: AOJu0Yy76u3j/tEx8XEIPI+wYnfl2io6ASOJdCpCAu3xdpV+P92axotw YU7Tc4U4919uXUNGKIQz646Eg3ZpCoUxY+hA+c194WZbYYGF+hZIOom8nVX4leTeD5dlNUZEY5W Ftv+qWqG1R9DVpsH3sy3eWQS21Zonl3ErISfobkpPmJaMm1+WsuLePzJGsd4= Precedence: bulk X-Mailing-List: syzbot@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:170f:b0:495:fed9:a84f with SMTP id 5614622812f47-4a4d051ebc3mr3730981b6e.27.1784401528247; Sat, 18 Jul 2026 12:05:28 -0700 (PDT) Date: Sat, 18 Jul 2026 12:05:28 -0700 In-Reply-To: <20260718123417.16339-1-liavalb@gmail.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a5bce78.f1649fcc.2a4208.0321.GAE@google.com> Subject: [syzbot ci] Re: Fix an imbalanced file ref count in the mmap syscall From: syzbot ci To: akpm@linux-foundation.org, david@kernel.org, jannh@google.com, liam@infradead.org, liavalb@gmail.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, ljs@kernel.org, mhocko@suse.com, pfalcato@suse.de, rppt@kernel.org, surenb@google.com, vbabka@kernel.org Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" syzbot ci has tested the following series [v1] Fix an imbalanced file ref count in the mmap syscall https://lore.kernel.org/all/20260718123417.16339-1-liavalb@gmail.com * [PATCH] mm/vma: fix imbalanced file reference count, properly abort mmap_prepare and found the following issue: WARNING in tear_down_vmas Full report is available here: https://ci.syzbot.org/series/63d42f9f-f249-4678-8916-5464a15accd6 *** WARNING in tear_down_vmas tree: mm-new URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git base: 3827fe994db98623a5a619a72f15f57bf8274deb arch: amd64 compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6 config: https://ci.syzbot.org/builds/f57e989a-6273-4413-b35d-20dab5a41e92/config syz repro: https://ci.syzbot.org/findings/8f36751f-0976-460a-b5ab-de97c9074c0a/syz_repro ------------[ cut here ]------------ !vma_is_attached(vma) WARNING: ./include/linux/mmap_lock.h:435 at vma_assert_attached include/linux/mmap_lock.h:435 [inline], CPU#0: syz.2.19/5813 WARNING: ./include/linux/mmap_lock.h:435 at vma_mark_detached include/linux/mmap_lock.h:455 [inline], CPU#0: syz.2.19/5813 WARNING: ./include/linux/mmap_lock.h:435 at tear_down_vmas+0x381/0x520 mm/mmap.c:1261, CPU#0: syz.2.19/5813 Modules linked in: CPU: 0 UID: 0 PID: 5813 Comm: syz.2.19 Not tainted syzkaller #0 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 RIP: 0010:vma_assert_attached include/linux/mmap_lock.h:435 [inline] RIP: 0010:vma_mark_detached include/linux/mmap_lock.h:455 [inline] RIP: 0010:tear_down_vmas+0x381/0x520 mm/mmap.c:1261 Code: 48 89 df e8 01 46 16 00 48 8b 44 24 18 48 39 03 0f 87 e0 00 00 00 e8 ce a8 a8 ff ff 44 24 04 e9 9a fd ff ff e8 c0 a8 a8 ff 90 <0f> 0b 90 e9 2c ff ff ff e8 b2 a8 a8 ff 90 0f 0b 90 e9 94 fe ff ff RSP: 0018:ffffc90003cdf7e0 EFLAGS: 00010293 RAX: ffffffff821dbb90 RBX: ffff888115e14b40 RCX: ffff888171f9bb80 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffc90003cdf920 R08: ffff888115e14b43 R09: 1ffff11022bc2968 R10: dffffc0000000000 R11: ffffed1022bc2969 R12: ffff888115e14a80 R13: 0000000000000001 R14: 0000000000000000 R15: dffffc0000000000 FS: 00007f15b88e36c0(0000) GS:ffff88818dc1c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f9033eab095 CR3: 0000000173ace000 CR4: 00000000000006f0 Call Trace: exit_mmap+0x4ca/0x9f0 mm/mmap.c:1320 __mmput+0x118/0x420 kernel/fork.c:1187 exit_mm+0x221/0x2d0 kernel/exit.c:610 do_exit+0x6cd/0x2360 kernel/exit.c:992 do_group_exit+0x22d/0x2f0 kernel/exit.c:1147 get_signal+0x121b/0x12c0 kernel/signal.c:3038 arch_do_signal_or_restart+0xbb/0x860 arch/x86/kernel/signal.c:337 __exit_to_user_mode_loop kernel/entry/common.c:66 [inline] exit_to_user_mode_loop+0x104/0x730 kernel/entry/common.c:101 __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:230 [inline] syscall_exit_to_user_mode include/linux/entry-common.h:318 [inline] do_syscall_64+0x353/0x580 arch/x86/entry/syscall_64.c:100 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f15b799ce59 Code: Unable to access opcode bytes at 0x7f15b799ce2f. RSP: 002b:00007f15b88e30e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca RAX: fffffffffffffe00 RBX: 00007f15b7c15fa8 RCX: 00007f15b799ce59 RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f15b7c15fa8 RBP: 00007f15b7c15fa0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f15b7c16038 R14: 00007ffe1b61d9f0 R15: 00007ffe1b61dad8 *** If these findings have caused you to resend the series or submit a separate fix, please add the following tag to your commit message: Tested-by: syzbot@syzkaller.appspotmail.com --- This report is generated by a bot. It may contain errors. syzbot ci engineers can be reached at syzkaller@googlegroups.com. To test a patch for this bug, please reply with `#syz test` (should be on a separate line). The patch should be attached to the email. Note: arguments like custom git repos and branches are not supported.