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 1F3E3C5AD49 for ; Sun, 8 Jun 2025 15:34:35 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 978AC6B0088; Sun, 8 Jun 2025 11:34:34 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 929E66B0089; Sun, 8 Jun 2025 11:34:34 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 840476B008A; Sun, 8 Jun 2025 11:34:34 -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 65EA36B0088 for ; Sun, 8 Jun 2025 11:34:34 -0400 (EDT) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id C1AA6C1A91 for ; Sun, 8 Jun 2025 15:34:33 +0000 (UTC) X-FDA: 83532630426.06.228D1B7 Received: from mail-il1-f207.google.com (mail-il1-f207.google.com [209.85.166.207]) by imf02.hostedemail.com (Postfix) with ESMTP id 2A03380009 for ; Sun, 8 Jun 2025 15:34:32 +0000 (UTC) Authentication-Results: imf02.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf02.hostedemail.com: domain of 3h61FaAkbAEIw23oeppivettmh.ksskpiywivgsrxirx.gsq@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.207 as permitted sender) smtp.mailfrom=3h61FaAkbAEIw23oeppivettmh.ksskpiywivgsrxirx.gsq@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1749396872; 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=fvmjFEQJ7WHJnAKAOrPBrNRIDj3V0nCEgS6r1TxVlcQ=; b=nxnjp3GiGNCtTa+XF+e46n3xXHu8lQlIiRIzXIs6vouSwCusCboy2vbjJITQMEallp24JO 832D58/AJ73nKREoHjxfJ88PN7lMVX3nTIjgk87o5ABwi9Z6MD6CObXNsVFeYvbNI3j//5 wL4IeFu1lxwfNg+xs3wbW3+CU5CnxDU= ARC-Authentication-Results: i=1; imf02.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf02.hostedemail.com: domain of 3h61FaAkbAEIw23oeppivettmh.ksskpiywivgsrxirx.gsq@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.207 as permitted sender) smtp.mailfrom=3h61FaAkbAEIw23oeppivettmh.ksskpiywivgsrxirx.gsq@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1749396872; a=rsa-sha256; cv=none; b=MnN0dtV6vmakSu9pin4SEQJtEYQno3PL33kM4Ol3SLFlShDKWAY4bMdB4H2uqAwdePV1bx dAFkbPgJyg8Ts1jE6Z96+7poIj7g66wkXGYK64lKg/BZBsNtSsgCiz1goadaWRJCGntM3O NBeIwov0gAlH9Xg7qRvTrPSvks+nbK0= Received: by mail-il1-f207.google.com with SMTP id e9e14a558f8ab-3ddd03db24dso17321045ab.2 for ; Sun, 08 Jun 2025 08:34:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1749396871; x=1750001671; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fvmjFEQJ7WHJnAKAOrPBrNRIDj3V0nCEgS6r1TxVlcQ=; b=DIu/lVp5p9qvTaYLl8BOWN6Qarcc1YWo6413rfvN4zCfzFqFZ3GBgz3+IlmsxYV/ra WXYmBRaaCVk3waa/ydK03vJPcTIZstnHVcEgkGo7mBOs5AwZx2qbE79wRBiprSCPb4VU 8AWOWhSstSg0h8OtTQGPIofL0dL+iMBVegX35sW/piYKqbkb5XbO569sFjpgGsmS2aFa 95my/f/ZLTYEUAtRYbMN/KGfqqFJb6ikbuUiZeZQ7z2BDFwtDZt1/sYNw6udcvkhlIB5 S1jgaWAAYwWqfrfEe1PjtU9ddCZ7tvHynnjDoN1PGF+X2DEPzSmLzyPyjB/bsJbNSgfH S6Gw== X-Forwarded-Encrypted: i=1; AJvYcCVivuvkBojUbcPsIKYYC/dMgpImqfTAk5T2G/tOtbSgVm5WZ+L3Ui0sEkcXk5xuU5ZRMUk4HE3lOA==@kvack.org X-Gm-Message-State: AOJu0YzhndIlY4AveW8wapFzeUxOaEv4yaijBoadNTGPVJ65U5d330k+ IcCDenLPCFnvV3vQm15h88Do5lgaOXTxLXv3SlOeW8rf0LwdYE30fEVCH1C629yi4PHasTTR4rl /EQm3dIKz4Aj1u6+H49tyuVIuHXQkObhxRTHE4LZtcqsxtt+gSJgOd+Xidnc= X-Google-Smtp-Source: AGHT+IEWIOIE0zZ+cAyq4LRpR1vM71PT3MHqhoewdfgnxr0E6bzEwMXEsEBz5B4OZz5by690b7nXQam121ahRwescIo6zkm6FSF2 MIME-Version: 1.0 X-Received: by 2002:a05:6e02:198e:b0:3dc:88ca:5ebe with SMTP id e9e14a558f8ab-3ddce3e3814mr106500545ab.4.1749396871251; Sun, 08 Jun 2025 08:34:31 -0700 (PDT) Date: Sun, 08 Jun 2025 08:34:31 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6845ad87.a70a0220.27c366.004e.GAE@google.com> Subject: [syzbot] [mm?] [ntfs3?] possible deadlock in upgrade_mmap_lock_carefully (2) From: syzbot To: Liam.Howlett@oracle.com, akpm@linux-foundation.org, almaz.alexandrovich@paragon-software.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, lorenzo.stoakes@oracle.com, ntfs3@lists.linux.dev, 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: 2A03380009 X-Rspamd-Server: rspam09 X-Stat-Signature: gimf5f4r9smbopiwy3sa8cobxoe8xcm5 X-HE-Tag: 1749396872-393353 X-HE-Meta: U2FsdGVkX1+WHKTZBwho1SA7LFPLYo7A++QkosN5m8MUAx6GvlZ2/DvLB5/nGLhBDUviIxND60Da7lADqNgV2ciYgL4SAFSh+NutwIg5vBJlrpsdeKYSpajoJL5WI/b62f4t//NZ3ise8wbslW4JIjqrRPYlNmHmWeXVaKG66FAnnay8i3l0kRvFXOsTZbQPztQmgez3dWDQjfUZkNkWA8EZFzVLIl/e46RvSH719CRqkTWtkmh9UmgNcILwXeGJLccdpjLvoyQJD8eSHXn/BRWp4NB722gXvBnFCyRGPY9YyOI1iNnLSdRkDUrbAim08tAN/PkiO95uk5qEwvfg8r1o+AQsszuNbw5yDR2osZ3fzEi8uxAGiePofcIV8Kvhiw5XP/8OA+Qt/KAaT588RhWAhE8ckgGvw5i8TNV9JEQnEpTyzLECMeJ3mO2S5eaiHSJPccoYsSaHbg1/H7ooZyLhrdP7vFzn4D2EkKzAfRR1DOf+BpVP8M0pPLnx3r665hBwKBZxQ7t1W53vbyfdyCKirr+D1oB0ef30Ww86Y+0UBtB9NRgiWL5t179cnd+ZigWwoR6zpnBpGdmLfpKYgB+9M7TVJNajmNOMVnS9TOZg/cGmf1dYABhCKhKHIu3hkgmph06lRCyXrlFYdOnzO//gjdqonteMX+CpMBTPJk3yieVyccUiYn9eyCKJDQ8G9N4y0Whq7AglXlu7XcqX8u6oAxgd6O9otEVO88xOiquJYBD+T3zITWTjA1PlAtIwp3JEo+GQWKmx6Ds07EEgnb2VuJj77on+Rc3POO9WCjTEe2jJ8NJBR7Kveg0cs+iX0J6OxbxHGL+3wkyrzRIKKez3SsG1jV/vL4VcG8wrwOf1oX841AnjOuGqfSAxVzgsAagAmmN9GHzzMTDJz1THm+T1OottqLWTD5DPE7NSjMqsGF1dBLSdencPvrNZzdMNZTmVxEj75pHz5iejkVo 4MijHYeD O/0ONwtMmB6/8nABvde5IifmUR1D+SFrJ9C4P4ATGOVjdBYbLVkpi7eoPvCVgScZgn5DOjPWBMZQ+nsvKonmFwAkkGIXm3dmjhgAtKs1Tpr2/BiX2iet/iuJjeTsQPtcVlrIcZrOtuo3csKaGXw+PRg3J5fpcOHpRTPKzAITTEjlbx5H/L6CXO79oKyxhPZpwb3h2f/WdANIZB1eEZOW+82f60841gIR3jho27HRQ+YOVP2fHUc0SACOEjexTHnC0LiqdnB8TOKtU2sOlx258vkt4sepZ2hgwjXz4a7pDOihGucJyDsahCZpooZj/GT8ebWg6wimf9lO9gUfvCI3TW4n/nu7LeA0SdBY7oXhC1cbXmUwtkLDBBemv8cO3XD/OVbKVFPpTUgftb57GntRjnyW6Jip4rCY8XpkkdpuUW5rOXJ+GPZtm1r8aMDEMGZaNZy1v03IoKH3iOo9PRngdWM7zW397udPg4OTOft94xbrAg7M6XnwHewMhU13XA9ZUGGmTAFok9l6KKhKW3zqRd/cT48OVOufosmcCnwnRLs3/fK1cw3RmlWoaaH5IaqqZDU1sAIJMe6EpIJ+wi5h7LDmqdp5kyNyuFwN6AyeLs7Yz3IDP9ccYsVkNO0lcUPKGVqrUl0Tnf7qn+CrM/gyH5WQcNpadugG30zLVZ6LqqePdIpZgiwqdZ2nmNSGl/ZBeg+r73qWQFW5sGx/aoKBQPW3qM6Iyywg1Hq/2mWyDiWjc30GuRNPHgdc3aS/VHYWnMjQ4EjxzjwPzgTpC5dkygTzRj7EAfIG3YGfbY1DLlRhDmWuka/I1BoBqY5iHDTlQWKXIu6V1z7Mpt/r4fhhUN0cgY4SoW3ntkdlprQI0ayXMYC7YSQpYn95r9zARVQq2Gbf0FC8vo/hufuQxCkld+iYbQ/zzFL5wn4OjAKvfYHl8N4mPbuTj6IIvMHASCc1osytzGGcch9l9tGQC9uNZWrTQRLA0 Ro5UWS8j Ms99ICCdFwgvhAoKPRkaEmoNlGbBpfYm5p/WPmk8emFqecKQmsy8g/Wt8/H+VivA/ldujWgbyppyrp3nu9qT1BeiKOHnPISvmuq36qHNjvK1GFx5miR8QOctAPrnn+cMIvzq8EhpYGZlCn2gKTQfKLREt3SkRWIutRtoER56qUjlHxAni/r+3d8pdsQHixPrLEpf/sLHgKWmjPNDs7CRRJRHgI7pgTkRb/axuZNX79gz0rMi8cyyRhroryA2ksdakwhyBiLwQh0ygrL6GqTOA6lLvBeViHTxSTQaXuab7jfBnvdvBI5qyGMzwgUfA6d8Gcjo5279/UwjRMj9T/I2l88X16ZkwCz1lbgUuGIxLPZhSSwq3ROgw5pYfctlnaLfCl7cTWWG5CUMXP73+CQZFoXXstLp+J7cXdPNG/7VS/p7QEEn9QGrpQ== 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: 1af80d00e1e0 Merge tag 'slab-for-6.16' of git://git.kernel.. git tree: upstream console+strace: https://syzkaller.appspot.com/x/log.txt?x=1653cc0c580000 kernel config: https://syzkaller.appspot.com/x/.config?x=82e79780b034d72f dashboard link: https://syzkaller.appspot.com/bug?extid=a91fcdbd2698f99db8f4 compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1667f40c580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1222e570580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/2108968c2c62/disk-1af80d00.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/fd3b30e8c62a/vmlinux-1af80d00.xz kernel image: https://storage.googleapis.com/syzbot-assets/a8aa2c824e68/bzImage-1af80d00.xz mounted in repro: https://storage.googleapis.com/syzbot-assets/ecf486535ea3/mount_0.gz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a91fcdbd2698f99db8f4@syzkaller.appspotmail.com ====================================================== WARNING: possible circular locking dependency detected 6.15.0-syzkaller-11802-g1af80d00e1e0 #0 Not tainted ------------------------------------------------------ syz-executor165/5834 is trying to acquire lock: ffff88803293c0e0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] ffff88803293c0e0 (&mm->mmap_lock){++++}-{4:4}, at: upgrade_mmap_lock_carefully+0xba/0x1c0 mm/mmap_lock.c:221 but task is already holding lock: ffff88807816e310 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:897 [inline] ffff88807816e310 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: ntfs_file_write_iter+0x78/0x820 fs/ntfs3/file.c:1160 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_write+0x96/0x1f0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:867 [inline] ntfs_file_mmap+0x525/0x730 fs/ntfs3/file.c:313 call_mmap include/linux/fs.h:2282 [inline] mmap_file mm/internal.h:167 [inline] __mmap_new_file_vma mm/vma.c:2398 [inline] __mmap_new_vma mm/vma.c:2460 [inline] __mmap_region mm/vma.c:2615 [inline] mmap_region+0x1221/0x1f30 mm/vma.c:2685 do_mmap+0xc45/0x10d0 mm/mmap.c:561 vm_mmap_pgoff+0x31b/0x4c0 mm/util.c:579 ksys_mmap_pgoff+0x51f/0x760 mm/mmap.c:607 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 -> #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_write_killable+0xa7/0x230 kernel/locking/rwsem.c:1588 mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] upgrade_mmap_lock_carefully+0xba/0x1c0 mm/mmap_lock.c:221 lock_mm_and_find_vma+0x10a/0x300 mm/mmap_lock.c:274 do_user_addr_fault+0x331/0x1390 arch/x86/mm/fault.c:1359 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 fault_in_readable+0x8e/0x130 mm/gup.c:-1 fault_in_iov_iter_readable+0x1b4/0x2f0 lib/iov_iter.c:94 generic_perform_write+0x7cc/0x910 mm/filemap.c:4161 ntfs_file_write_iter+0x71c/0x820 fs/ntfs3/file.c:1197 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x548/0xa90 fs/read_write.c:686 ksys_pwrite64 fs/read_write.c:793 [inline] __do_sys_pwrite64 fs/read_write.c:801 [inline] __se_sys_pwrite64 fs/read_write.c:798 [inline] __x64_sys_pwrite64+0x193/0x220 fs/read_write.c:798 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 ---- ---- lock(&sb->s_type->i_mutex_key#14); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#14); lock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz-executor165/5834: #0: ffff888034c60428 (sb_writers#8){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3092 [inline] #0: ffff888034c60428 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x211/0xa90 fs/read_write.c:682 #1: ffff88807816e310 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:897 [inline] #1: ffff88807816e310 (&sb->s_type->i_mutex_key#14){+.+.}-{4:4}, at: ntfs_file_write_iter+0x78/0x820 fs/ntfs3/file.c:1160 stack backtrace: CPU: 0 UID: 0 PID: 5834 Comm: syz-executor165 Not tainted 6.15.0-syzkaller-11802-g1af80d00e1e0 #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_write_killable+0xa7/0x230 kernel/locking/rwsem.c:1588 mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] upgrade_mmap_lock_carefully+0xba/0x1c0 mm/mmap_lock.c:221 lock_mm_and_find_vma+0x10a/0x300 mm/mmap_lock.c:274 do_user_addr_fault+0x331/0x1390 arch/x86/mm/fault.c:1359 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0010:fault_in_readable+0x8e/0x130 mm/gup.c:2227 Code: a9 00 00 00 0f 01 cb 0f ae e8 4d 85 f6 40 0f 95 c5 4c 89 ff 4c 89 f6 e8 40 e5 b9 ff 4d 39 f7 0f 97 c0 40 84 c5 74 43 4d 89 f5 <41> 8a 45 00 88 44 24 07 49 81 e5 00 f0 ff ff 4d 8d a5 00 10 00 00 RSP: 0018:ffffc900044efa88 EFLAGS: 00050202 RAX: ffffffff82066801 RBX: 0000000000000140 RCX: ffff88802bed5a00 RDX: 0000000000000000 RSI: 0000200000002000 RDI: 0000200000002140 RBP: dffffc0000000001 R08: ffff88802bed5a00 R09: 0000000000000002 R10: 0000000000000001 R11: 0000000000000000 R12: 00007ffffffff000 R13: 0000200000002000 R14: 0000200000002000 R15: 0000200000002140 fault_in_iov_iter_readable+0x1b4/0x2f0 lib/iov_iter.c:94 generic_perform_write+0x7cc/0x910 mm/filemap.c:4161 ntfs_file_write_iter+0x71c/0x820 fs/ntfs3/file.c:1197 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x548/0xa90 fs/read_write.c:686 ksys_pwrite64 fs/read_write.c:793 [inline] __do_sys_pwrite64 fs/read_write.c:801 [inline] __se_sys_pwrite64 fs/read_write.c:798 [inline] __x64_sys_pwrite64+0x193/0x220 fs/read_write.c:798 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:0x7effea34b459 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 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:00007fffba5c42c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000012 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007effea34b459 RDX: 000000000000fdef RSI: 0000200000000140 RDI: 0000000000000006 RBP: 0000000000000000 R08: 0000000000000000 R09: 00007fffba5c4300 R10: 000000000000fecc R11: 0000000000000246 R12: 00007fffba5c4300 R13: 00007fffba5c4588 R14: 431bde82d7b634db R15: 00007effea39403b ---------------- Code disassembly (best guess): 0: a9 00 00 00 0f test $0xf000000,%eax 5: 01 cb add %ecx,%ebx 7: 0f ae e8 lfence a: 4d 85 f6 test %r14,%r14 d: 40 0f 95 c5 setne %bpl 11: 4c 89 ff mov %r15,%rdi 14: 4c 89 f6 mov %r14,%rsi 17: e8 40 e5 b9 ff call 0xffb9e55c 1c: 4d 39 f7 cmp %r14,%r15 1f: 0f 97 c0 seta %al 22: 40 84 c5 test %al,%bpl 25: 74 43 je 0x6a 27: 4d 89 f5 mov %r14,%r13 * 2a: 41 8a 45 00 mov 0x0(%r13),%al <-- trapping instruction 2e: 88 44 24 07 mov %al,0x7(%rsp) 32: 49 81 e5 00 f0 ff ff and $0xfffffffffffff000,%r13 39: 4d 8d a5 00 10 00 00 lea 0x1000(%r13),%r12 --- 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