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 394ADC54E60 for ; Tue, 19 Mar 2024 09:52:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id ACAE56B009A; Tue, 19 Mar 2024 05:52:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A7B5B6B009B; Tue, 19 Mar 2024 05:52:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9429D6B009C; Tue, 19 Mar 2024 05:52:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 855DB6B009A for ; Tue, 19 Mar 2024 05:52:19 -0400 (EDT) Received: from smtpin10.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id 2D84D120285 for ; Tue, 19 Mar 2024 09:52:19 +0000 (UTC) X-FDA: 81913323198.10.CABC39F Received: from mail-il1-f197.google.com (mail-il1-f197.google.com [209.85.166.197]) by imf24.hostedemail.com (Postfix) with ESMTP id 8D1EB18001B for ; Tue, 19 Mar 2024 09:52:17 +0000 (UTC) Authentication-Results: imf24.hostedemail.com; dkim=none; spf=pass (imf24.hostedemail.com: domain of 3UGD5ZQkbAC0bhiTJUUNaJYYRM.PXXPUNdbNaLXWcNWc.LXV@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.197 as permitted sender) smtp.mailfrom=3UGD5ZQkbAC0bhiTJUUNaJYYRM.PXXPUNdbNaLXWcNWc.LXV@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=1710841937; 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=wgksWobu6Y4B5YtXN/SFJIBHO1gc/F7nv1xG78u++sk=; b=50eAc30RX9VwBV4HTvZS9ytXjMM1PhCWYsvrr2SmdiLgq0yL/xhpu3owt0HA+eYD2ehkC6 epKZHXTTxF+8O9ueuN71Dg7hfJ3eGLWWZjIwhXrZbAkiOGRMM4qV6F579yDrNm9at0h6FV NDbwQdoK0qfg3dqdNcMbYNhkRFUzYx4= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1710841937; a=rsa-sha256; cv=none; b=n8vgk5RhFX3N1qrfBZ7bYevFhDPZTqYJHy/AHUmhE1erPgSEpqxaWL+cj4eEsd85RY7YZT OqaftrYk9EYWmoPW5TQ8KK0fcra9tCo6ASYAZVcwt805Biyl31QzybW+HGSK+aq/twJXqy wRKCY3hTubhf/QzbASH27zWO1Mv/a8I= ARC-Authentication-Results: i=1; imf24.hostedemail.com; dkim=none; spf=pass (imf24.hostedemail.com: domain of 3UGD5ZQkbAC0bhiTJUUNaJYYRM.PXXPUNdbNaLXWcNWc.LXV@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.197 as permitted sender) smtp.mailfrom=3UGD5ZQkbAC0bhiTJUUNaJYYRM.PXXPUNdbNaLXWcNWc.LXV@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none) Received: by mail-il1-f197.google.com with SMTP id e9e14a558f8ab-3673c792f3eso13108585ab.2 for ; Tue, 19 Mar 2024 02:52:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710841937; x=1711446737; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=wgksWobu6Y4B5YtXN/SFJIBHO1gc/F7nv1xG78u++sk=; b=AbPTPXU6/W7FghPizHu8t1mOaPuyTxGMOzKXmoJ7LqaXbkjlNq5BS6OzkoPFa44/nx ozL2Y6duTOsGY/BLi/VQM/GCgMTFvqQrjOj/nqT76uKr6Cl50QnBIMcziz68gMRu0mFJ 612f9Ro8ONaKKNjIkVpdTh71cGmrOVHI73FtAf1VsmAX8Rfssb7AYS/3nW7JCZM70FNU PzFIEcJqrHsvBGfKdPZvhrm9J0WN+sGqRWwYZsBuV3rCmLHoGlxsM4F6b47ono012cj2 VW70WWA7CxmCJfvn7P2vNkeMDkhAL/fSYzJ8SeVqeOZKDo0vvBDGDKklOMdKDTVHGoJJ QLJg== X-Forwarded-Encrypted: i=1; AJvYcCWrCqVneD7avc5e4wlqdQVHEwb5iDClIokrzr/9n19JrB3T72Pt/agLSA3NfDfOqJ7048SDYQYNYuqiF/dmvUUO5XE= X-Gm-Message-State: AOJu0Yy/DlZEw3RkiDNHQC+giAGell5KcC6djW48Zv7rhDdr/6y0aBfv fME9tEvV6vQnD7Ozp8k3Ko4zxpGhMRQg/KAWbumh7zNvvTjLV1oALH8whGEuCibCmx3XgMfFGsw FWpLfEUru8JzlPvDev18bw6GPgg39pPx9ylimI7lO0ow+HSM2swX9MXg= X-Google-Smtp-Source: AGHT+IG/wGs4aWlyM2S68c62kL+A3QQGcB9D+htUYVkg+wDZ/gF2SIPxTnc0Tf8OPyAnTxwviiqLVBAUZlbJ0S22lA0F8J5qX2Im MIME-Version: 1.0 X-Received: by 2002:a92:3601:0:b0:368:4f35:92d8 with SMTP id d1-20020a923601000000b003684f3592d8mr51852ila.0.1710841936832; Tue, 19 Mar 2024 02:52:16 -0700 (PDT) Date: Tue, 19 Mar 2024 02:52:16 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000e97f090614006d76@google.com> Subject: [syzbot] [mm?] possible deadlock in move_pages From: syzbot To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" X-Stat-Signature: qt6s9jn1g4ac63wdermmmb7rax158aut X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 8D1EB18001B X-Rspam-User: X-HE-Tag: 1710841937-946289 X-HE-Meta: U2FsdGVkX1+2c3JPq5nD+qjgCaSlgZkckNXUDYWWaiJo4Odf1mbWVh7pP+ydNYVxB4BtYM6zFdxFNEoEO1HzACiEd3kahv6ijrvPImnFZXlecLKB2BMZf3aMgCJkvBGnnBtOagNxxgguYfYY8My6ew2AehoJ0AJWH7Ie+3ijJsFjPGY1ORk+ItMI+5y+PgxC1OmUZjVcavIIBJV6dQX9gKFlwOZqgQrbKPmQRuD0TTy4y6PqORc6sa2xpQKAiVCCZV6lPDvYm66DDbRszzJqNM9QUTK9kerfq5i6nsxcHdpEt5admKtCo1HZo6i62simJCCq7mzjZZS7no3bNs/6J6Ej1PAigciJ53oT12QnhkwdzL9x0ziDbtsvyRg5TnaMJ4/C3FGf7GC+DaejpAh/o6xDsQCo/qMxJe3B0VyjiBW+5P+LuB0tlmRU4Uxvu2no0nD320P05eVHqUiWL2hwETXTQaPFRIjsdnzQ6hmrAgdpKPAeaALcgRkLOcpGHIOWoesQ6jkXc4vSqXuaqejdg3zb/lBCNCztlfw2hpNAIxVQ0GVmK+hmYad3rF1A7bquRnThqW+GzMhIbIB0NvqvCbtqD0fymsZKVYX16JIhKaI7P+0mdyUadP4RFE/XwnFKYa+2KMkNv7seGvngOOYhILY7CNemYaq8SIKi6ME+e3CUqJzaawoJWx5uGg15lqkpSxtnZm7ESYsUMRd7zphUDCweAnmErqjxYYRXmGa3dY4l6V8FkD+eWZOsbVDvlgxEP2LTYUQnqlDcBBy5DoJr+JfdEWzX2BWcUb+a4IYbEBuIV43PgdcOEW5lAr1UFCzItyubAqsNiu4ovg2xUY0SJnspgFSIkW/mS/qnFhtLYQBO5h5JBtFFTGMcrBclSYpFfsX49iBP1Z3tsJmCgucGvVvbpP0K5qtQyhaTjgX1x3ljl6StxLigLKe/BbG3ZYdLFOtU9H0+zGV3Lb/sfiy qmG56kXD 46I2qhbGlyave1sxsmUmDu/UGHYS5ybSfi+S3I53kD/dFNq4ARty67It7FegdinDCzbbIG+Lu+IbqsRezb6TVg4c9Hx5H/Jc5PJaOkg4j5Cd0rwqIj1Mr6QJquaTw/ilrrzNPZqdyxpZP2QpcHUM2wbOVVTBWOQTDrTXsFsEl9LyvOcCmUbhu5FhIR/cndZ4eUUgkvxcU2Yx64tydx1cjeCc7CD1E2FWb+pnVa0eqDbdXiaUp9Td9MBrdQH6oPK3he34lzn4ygIxBRRHuNieFxxGLuLg+FwtN+MGkc1e7SCSK/v0q8bP7UxfXFh6L1KitjsxvxrTn4F2358Rm4PFDOwy5r8HNr4kPwCrnKmRYf0W4EzQ+WRE1fp8NDlys5EBZMNXmkXO0BktQX1Vka7qjAU5Vcs4ym4sQLKCKI4H2PzWQ8se4iAbjFUWK5UrFC0/3UsoEwywqREkZ4AlBD44rb3WjfnzeJ5IZJUfWITHW7sdOC+yDI941sWf6Is9H3NfUYYj1BB5ekiJczH6Wtfx7O99erOll2JY71fXp9Z72nyPsIBwxzQRC0aM3o6Ae58k10SU0rGw1hm7Y/0yq4WuIXfulPDBHVU8NZ9SrQ83kK3WlRehOrSab+sQA178XYovH0qEVKNGcMwCnIA7bxGD+hdKygQiy+zTUVboDUdUqECzV3OXK1+UkIpU602E1CV3EKMPsHXlo7VvtfZrsEdLE0DLWOq/8W+wWJv8e3JyYV5aHnBVfbsUEEMxCsdoKgg5IaM66FtsgaCdNxtbznc1pWMO2y/2G7jYQ9nGWW4GVUkTHZQU04kPgX8gFVOTsLwu80dUC8sexr0LW2hxLESmNqV3hUJlXtz46Xn2RgqL6CyNOsP5cwNSPyFfxUaTdeyKHwHZAjvN32k7X97Sw9RMMbyB/DG87ICyvN92xiRZWjTnSBchivVVI42IgFx70ZGf99Ja+M8ioY5UnkDyKQlFXsUbsr8r+ m5ZcqpVB 8Q5pm7Nm28ZjGd9oxMS19dFPTPN42zZuoRnuhdxZRmI/RZ44l4Cljtcxk5rgw+62e2XlIPiWoZ9TKPAjXNOa5AckgaQyAjSk4NTNyWdupftMN113DPJB47XeOeCoQN5Gob5NKWbbBt/1IIPkeDfwjj+W5SWutyFw6fjj5pJbeDb180WYzgjH1BmpsyYRXIhlnLbqfvQg6OGrU7fCnp+GuPrEkaeTE/noklKs8+P1S4iK6z/g4y9rsrRnqLZC12uKT4S/japIhEr/hABWZXzgdHRSjudS8PAD7UYTGLw0Wp2/yKA3O1vqdssFDsxf/dARHT/hdv9nz5fCZa57QH2uJAf8/idPORRAWGMs+LlaZK0= 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: e5eb28f6d1af Merge tag 'mm-nonmm-stable-2024-03-14-09-36' .. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=160dc26e180000 kernel config: https://syzkaller.appspot.com/x/.config?x=4ffb854606e658d dashboard link: https://syzkaller.appspot.com/bug?extid=49056626fe41e01f2ba7 compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10f467b9180000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173b7ac9180000 Downloadable assets: disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-e5eb28f6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/a5c7ad05d6b2/vmlinux-e5eb28f6.xz kernel image: https://storage.googleapis.com/syzbot-assets/531cb1917612/bzImage-e5eb28f6.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+49056626fe41e01f2ba7@syzkaller.appspotmail.com ============================================ WARNING: possible recursive locking detected 6.8.0-syzkaller-09791-ge5eb28f6d1af #0 Not tainted -------------------------------------------- syz-executor258/5169 is trying to acquire lock: ffff88802a6d23d0 (&vma->vm_lock->lock){++++}-{3:3}, at: uffd_move_lock mm/userfaultfd.c:1447 [inline] ffff88802a6d23d0 (&vma->vm_lock->lock){++++}-{3:3}, at: move_pages+0xbab/0x4970 mm/userfaultfd.c:1583 but task is already holding lock: ffff88802a6d2580 (&vma->vm_lock->lock){++++}-{3:3}, at: uffd_move_lock mm/userfaultfd.c:1445 [inline] ffff88802a6d2580 (&vma->vm_lock->lock){++++}-{3:3}, at: move_pages+0xb6f/0x4970 mm/userfaultfd.c:1583 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&vma->vm_lock->lock); lock(&vma->vm_lock->lock); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by syz-executor258/5169: #0: ffff888015086a20 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:146 [inline] #0: ffff888015086a20 (&mm->mmap_lock){++++}-{3:3}, at: uffd_move_lock mm/userfaultfd.c:1438 [inline] #0: ffff888015086a20 (&mm->mmap_lock){++++}-{3:3}, at: move_pages+0x8df/0x4970 mm/userfaultfd.c:1583 #1: ffff88802a6d2580 (&vma->vm_lock->lock){++++}-{3:3}, at: uffd_move_lock mm/userfaultfd.c:1445 [inline] #1: ffff88802a6d2580 (&vma->vm_lock->lock){++++}-{3:3}, at: move_pages+0xb6f/0x4970 mm/userfaultfd.c:1583 stack backtrace: CPU: 2 PID: 5169 Comm: syz-executor258 Not tainted 6.8.0-syzkaller-09791-ge5eb28f6d1af #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:114 check_deadlock kernel/locking/lockdep.c:3062 [inline] validate_chain kernel/locking/lockdep.c:3856 [inline] __lock_acquire+0x20e6/0x3b30 kernel/locking/lockdep.c:5137 lock_acquire kernel/locking/lockdep.c:5754 [inline] lock_acquire+0x1b1/0x540 kernel/locking/lockdep.c:5719 down_read+0x9a/0x330 kernel/locking/rwsem.c:1526 uffd_move_lock mm/userfaultfd.c:1447 [inline] move_pages+0xbab/0x4970 mm/userfaultfd.c:1583 userfaultfd_move fs/userfaultfd.c:2008 [inline] userfaultfd_ioctl+0x5e1/0x60e0 fs/userfaultfd.c:2126 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:904 [inline] __se_sys_ioctl fs/ioctl.c:890 [inline] __x64_sys_ioctl+0x193/0x220 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xd2/0x260 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x6d/0x75 RIP: 0033:0x7fd48da20329 Code: 48 83 c4 28 c3 e8 37 17 00 00 0f 1f 80 00 00 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd1244f8e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffd1244fab8 RCX: 00007fd48da20329 RDX: 00000000200000c0 RSI: 00000000c028aa05 RDI: 0000000000000003 RBP: 00007fd48da93610 R08: 00007ffd1244fab8 R09: 00007ffd1244fab8 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007ffd1244faa8 R14: 0000000000000001 R15: 0000000000000001 --- 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 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. 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