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 8D9A5CF6496 for ; Sat, 28 Sep 2024 22:34:26 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E8EDC6B0129; Sat, 28 Sep 2024 18:34:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id DEF388D0001; Sat, 28 Sep 2024 18:34:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C42C36B012C; Sat, 28 Sep 2024 18:34:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 9ED8C6B0129 for ; Sat, 28 Sep 2024 18:34:25 -0400 (EDT) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 2C83F1405C5 for ; Sat, 28 Sep 2024 22:34:25 +0000 (UTC) X-FDA: 82615602090.05.45A20C9 Received: from mail-il1-f197.google.com (mail-il1-f197.google.com [209.85.166.197]) by imf23.hostedemail.com (Postfix) with ESMTP id 6D500140009 for ; Sat, 28 Sep 2024 22:34:23 +0000 (UTC) Authentication-Results: imf23.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf23.hostedemail.com: domain of 3boT4ZgkbAJcJPQB1CC5I1GG94.7FF7C5LJ5I3FEK5EK.3FD@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.197 as permitted sender) smtp.mailfrom=3boT4ZgkbAJcJPQB1CC5I1GG94.7FF7C5LJ5I3FEK5EK.3FD@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1727562726; 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=UUzM10drJEh/Fg2vpUbxj6xsaSQCsnottVwN/MjWrFM=; b=3wnLhNFpT5kcmuVGv5/LmHRIIrQ+r4UiYF0kO++qB0l/RpcugVx1we3mEhtxycqvorQCW7 uxfnv4uiPdTiC3H9m4dYdxD1Kq1R8UkiEukm+SkZvqQZqkoDYkYps3lT2Kw8pKt2wd4YLb X5fTIns/D7KMX2vrnNGyWXmDHcN1wBE= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1727562726; a=rsa-sha256; cv=none; b=3ZcfSSPQxb+FJDyXCy9fLQS8JsMKkU94jhNi+74czQ8sEOztK8aMJWv521XvlEPg2lZah3 82O2ywzVkXmo2kb7bqxVkQabsCOuLOikJLgOr0dQyOstg5TpcQUzUViKr89wGPArG0Vw3n k+ZTp3mFCwZJ1qMr7ZOSC5T6keXm3Cc= ARC-Authentication-Results: i=1; imf23.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf23.hostedemail.com: domain of 3boT4ZgkbAJcJPQB1CC5I1GG94.7FF7C5LJ5I3FEK5EK.3FD@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.197 as permitted sender) smtp.mailfrom=3boT4ZgkbAJcJPQB1CC5I1GG94.7FF7C5LJ5I3FEK5EK.3FD@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-il1-f197.google.com with SMTP id e9e14a558f8ab-3a3481b26d6so16941595ab.2 for ; Sat, 28 Sep 2024 15:34:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727562862; x=1728167662; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UUzM10drJEh/Fg2vpUbxj6xsaSQCsnottVwN/MjWrFM=; b=oEgjTry7sip0SIOUj+Ak5/RjkPduEHMo31ENqK+JJXbV1tbTZrrlOLr0lETdiPX7/5 glHy5TkjYVCuge0NvdAe9UX3DgiJglvuTX1M6HZa/+ZJOVTwpmxF7kxwwB8bobg0hT4L vJ6uycwMErLqnHWQhwFVwuuS7XhTLrmdNAZg6VZd47+W4IvQqRNPdkOUIrdrwq4I21dK hcXxluzcNRLLX1YBAmDytGSUsnGxY4T1yPMLP7kaHqe5wmsAn0C2WPZcM7mLuBdQef9d i0+ftr3VXsmq3xWmAAupeQtO3F84VgPbydhchp30HF16qaR+NYhh3hDKwzNRO79peAgc 6zJg== X-Forwarded-Encrypted: i=1; AJvYcCWesElKRfXgts/oEFf4IRK7P9gG6p5q3n4hWGKbyJfgI8OPnSDT4dkG2RkBprKTVx4n6a5z7cMMYQ==@kvack.org X-Gm-Message-State: AOJu0Yx+tflQxyKuinJefCyoo16WQI9IrU56MCR3f5QHT9WkUiV9QIch bZmADh+41gU4roJM6A5x6wkEnat9dQxLL6OLNZBiryEbLbRSkE9rwzW4k8srN1sAd+NFeKufb6d A2nHfAP3Li88Wd4xh9smb4MUZTVBEQ5Ut0riLXv2/On/eW/9AxCbSwWY= X-Google-Smtp-Source: AGHT+IGd+7J6RInzD0A8R39JC90iY3mjpGYSK5F64kSfNmIFWuqD6W7FaD+sySiTc7OBRdciJmLH+u7yJeQdv8unGL80lZndU5eD MIME-Version: 1.0 X-Received: by 2002:a92:c54f:0:b0:3a0:9952:5fcb with SMTP id e9e14a558f8ab-3a3451af2d8mr70599945ab.17.1727562862415; Sat, 28 Sep 2024 15:34:22 -0700 (PDT) Date: Sat, 28 Sep 2024 15:34:22 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <66f8846e.050a0220.aab67.000b.GAE@google.com> Subject: [syzbot] [mm?] possible deadlock in upgrade_mmap_lock_carefully From: syzbot To: akpm@linux-foundation.org, hughd@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 6D500140009 X-Stat-Signature: 5mj5m9zajr7qr79oyc6jppus816fitd3 X-Rspam-User: X-HE-Tag: 1727562863-648713 X-HE-Meta: U2FsdGVkX1+1OdJQYBfLyH169jxXUn9G+jmQRkjSwT8WDoiRToimjKxyan3AA1bYpFy8xITGHcGAGki55bCPKNlvoGiopqH6CsnE9J0MOUxxdNSkSgkXut8Hd4qZXlH1yfNvfL56I0rAgMaew6fMy4uQfkYiunLK1Qa1hlPRE9fvYZEcjEan7g+okK0SJMfQTZj6zN0EPdW2/yV/hFyefQ9HnvkhRVPi+1hQm9d6qocc6AJPDu1LXPIRdThi6XTa5t9VNIsDx4JZrkjdSCoYF4woqNLnO3bd+vp7sETWHI6dkEFMfuMTco9+5aE2Clz5YvVlrPctzY6iCG3q3b6cf0J1pdjikc9T6T9RgaGXKf6YguImnLkzXRW8hkTMNK1cadcy6eomVFG4f3DE55UgCpsgu49tOqRljrXzpugKsljl/uayVCSNaBKSPQgKZtVp9lVP8iCj9+UAlRHfr7FFhJMz+hPyUWfYYeMK4hKX7g8wPU4J3R+AMFVsM/1Q/ifSwETjoj2Qbh3BG9gLydJmZiMadeOLfCmiluJgkOavXapB8EZEe6lKIE4JMen+4Zbq98xomRwdHiIbCWgg5K3AN20Or56WwlImsDu4AX/d4QxfrHKNeg0x5XipIUAvyhyASsBN2XETcsnIIvipBIRuXX9Ukjjl4Bzf3E8MlKKgbBY2ICHfMGPk3Rh+tsjrlfBn4vCAL62jBV8gG3xmCy6m+2ucX0ho6cPch/Az6NKr9gEsYwRX1I2xbZm/8C9UhoAW9Rq8zWmDtsjNiXf2/GE7y62TddYevajjtzjpE1bb0xJC4j7YikPncJf0aBazSKlZKOIULg777F8ytAj1Y1OBPbaIg4Fiz1GEnztvd5nSllzOXvPehk2nypM2piSXeCkm3fHyS8KsCoxeRIQJR0YGcljds+rFrlTGye3owFegdTCuSAPNh1r++eed/LGXe/8gUN9bsWEl8TMqULeebkA JUro9dC7 gcR4Sfd/6J/FB1vGMGjGEr3X5NCe3SPNW6Kt72CaDYwkIous1NV/Gpr88Fc79arRqjIAE5lcfIU0xIO+75ylOWAsGrnfuOdvQcbtGef3L9eizuwUx2yXReQpcH8R3Srpe7kAUB1Ws9vr8ZWUKZH36MM5Ky0zeDkfxQ5qI0cGXeTRcmlwLgN+oADt9bBB80hVgjwdEcp9bSq4vWxKhETK+g8rxp2fS/cNbJyMmh9Lb7VpKuy0UtSFFh6K0Xltc5zRh/YklPBsn9OGVWbVPpKUltR9XBKGEIhVKxHBskZwIKFIhfFv1zQKlwedF+BOuGqEsmIko9Lo2i5zrIjM55WFAs56uDM/qOy2fU7VGK3i1WAz9TfyFOOs8LYdncORbmtMLQimsKtUGHengL6TSPpaW06wBi/rqjG3pw295mYwy+zHPnyt5DKIMFlNr6zjk71cStLbu+BGQhGoUqYpsL7gG2B77ifgaVGiOGmv1UfYrh7FXsd6+1U9Y186+9MCoBVKTviLvrnQezBMfFK3ty0zWjh2tyCVylg9nPKVlqAjn492G5YEQ7Z2YChqvyQabU8zZofranX1MrjNIxLSMkJFxeOkK/QRDpV+B6LfAqly7V0teOdl9d/Z8yKYdRZ6q0ju+OGvDxAcYvbqNVBRCQ2Xp75NahFDcdkCO6GChdOFTnQUPW44bNbblyUhIfZuJDVFGR9SR24H0Z5tuBWajHUMUdhQtoSQ7BX0b8gawyuVacL9PJLO/cvK3C60EG2prRuWAQH51kKN44wGhHQ3XcXvycUxRYgObPX6cLYbKjw6wquKJFECfqTPq601ShM2DPUtexgZOmf1gDoBYRar80nVbxu+AhOJotbSNnv5fmQmdcMB2D/HDrm9e7oAdODYNNd6dwxlAp/yWVY7jKL1t55TCpj+IBamrHvOsJBRqAbrRWhBThqf+1GjdOTOS/dwYumGP5tbtPvB5U2SuJjiWV6+asp1ERbkY rBPGUIyb UmIF1c2X6FhlRheKTwBUv8r5liCkCPLk5Tofo7Zkqdo7zuKwZ+49DDb69p6XU5unvz+NctcgYjVkwmbeI9GHJDyRWOpyM+xHew95QvQmM1tJVosZFgisFtUf3LreASH6oHNt+KMK27xbC6/yE1vxno4FNaNrHJG23Wue6bW0B+/6Qik/ID2IYBfbB3/B/3lFXp2NuzmuhATK8CRiA10F4YAT5J4wUiaMqCd4KJ5UaPfpAoLv9rm2NABdzKEnmrCMZ7Sz+tKAV42wwPt1NyrPPaxJn4jz1FfoGuk2vj/iMlc2BoqjeRXlaEn9Krb9LFvXG2AEise4VErtjr6P523O1aklRX0DjEskWdgNUKsQiQ2bDPJGIctS635V6uEXrunRz2/msgCc/uYHs8U3kARnP3QB/s06YATo 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: 684a64bf32b6 Merge tag 'nfs-for-6.12-1' of git://git.linux.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11d9299f980000 kernel config: https://syzkaller.appspot.com/x/.config?x=bd75e1a00004094f dashboard link: https://syzkaller.appspot.com/bug?extid=a6456f6334aa19425886 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/72e96b8890d5/disk-684a64bf.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/27bdd881ea38/vmlinux-684a64bf.xz kernel image: https://storage.googleapis.com/syzbot-assets/315166afeb3a/bzImage-684a64bf.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a6456f6334aa19425886@syzkaller.appspotmail.com ====================================================== WARNING: possible circular locking dependency detected 6.11.0-syzkaller-10547-g684a64bf32b6 #0 Not tainted ------------------------------------------------------ syz.3.2933/22916 is trying to acquire lock: ffff88807bf96a18 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] ffff88807bf96a18 (&mm->mmap_lock){++++}-{3:3}, at: upgrade_mmap_lock_carefully+0xb6/0x160 mm/memory.c:6132 but task is already holding lock: ffff888078651ce8 (&sb->s_type->i_mutex_key#12){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:815 [inline] ffff888078651ce8 (&sb->s_type->i_mutex_key#12){+.+.}-{3:3}, at: shmem_file_write_iter+0x80/0x120 mm/shmem.c:3211 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#12){+.+.}-{3:3}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5822 down_write+0x99/0x220 kernel/locking/rwsem.c:1579 inode_lock include/linux/fs.h:815 [inline] process_measurement+0x439/0x1fb0 security/integrity/ima/ima_main.c:250 ima_file_mmap+0x13d/0x2b0 security/integrity/ima/ima_main.c:455 security_mmap_file+0x7e7/0xa40 security/security.c:2977 __do_sys_remap_file_pages mm/mmap.c:1692 [inline] __se_sys_remap_file_pages+0x6e6/0xa50 mm/mmap.c:1624 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3158 [inline] check_prevs_add kernel/locking/lockdep.c:3277 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3901 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5199 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5822 down_write_killable+0xab/0x260 kernel/locking/rwsem.c:1590 mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] upgrade_mmap_lock_carefully+0xb6/0x160 mm/memory.c:6132 lock_mm_and_find_vma+0x107/0x2f0 mm/memory.c:6185 do_user_addr_fault arch/x86/mm/fault.c:1361 [inline] handle_page_fault arch/x86/mm/fault.c:1481 [inline] exc_page_fault+0x1bf/0x8c0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 fault_in_readable+0x165/0x2b0 fault_in_iov_iter_readable+0x229/0x280 lib/iov_iter.c:94 generic_perform_write+0x259/0x6d0 mm/filemap.c:4040 shmem_file_write_iter+0xf9/0x120 mm/shmem.c:3221 new_sync_write fs/read_write.c:590 [inline] vfs_write+0xa6d/0xc90 fs/read_write.c:683 ksys_write+0x183/0x2b0 fs/read_write.c:736 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 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#12); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#12); lock(&mm->mmap_lock); *** DEADLOCK *** 3 locks held by syz.3.2933/22916: #0: ffff8880391b2478 (&f->f_pos_lock){+.+.}-{3:3}, at: fdget_pos+0x24e/0x320 fs/file.c:1187 #1: ffff888043608420 (sb_writers#5){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2931 [inline] #1: ffff888043608420 (sb_writers#5){.+.+}-{0:0}, at: vfs_write+0x224/0xc90 fs/read_write.c:679 #2: ffff888078651ce8 (&sb->s_type->i_mutex_key#12){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:815 [inline] #2: ffff888078651ce8 (&sb->s_type->i_mutex_key#12){+.+.}-{3:3}, at: shmem_file_write_iter+0x80/0x120 mm/shmem.c:3211 stack backtrace: CPU: 1 UID: 0 PID: 22916 Comm: syz.3.2933 Not tainted 6.11.0-syzkaller-10547-g684a64bf32b6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2203 check_prev_add kernel/locking/lockdep.c:3158 [inline] check_prevs_add kernel/locking/lockdep.c:3277 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3901 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5199 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5822 down_write_killable+0xab/0x260 kernel/locking/rwsem.c:1590 mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] upgrade_mmap_lock_carefully+0xb6/0x160 mm/memory.c:6132 lock_mm_and_find_vma+0x107/0x2f0 mm/memory.c:6185 do_user_addr_fault arch/x86/mm/fault.c:1361 [inline] handle_page_fault arch/x86/mm/fault.c:1481 [inline] exc_page_fault+0x1bf/0x8c0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0010:fault_in_readable+0x165/0x2b0 mm/gup.c:2235 Code: b3 ff 4c 8d b3 ff 0f 00 00 48 89 d8 4d 01 e6 49 81 e6 00 f0 ff ff 49 39 c6 72 6b e8 95 cd b3 ff 4c 39 f3 74 6e 4c 89 64 24 10 <44> 8a 23 43 0f b6 04 2f 84 c0 75 18 44 88 64 24 40 48 81 c3 00 10 RSP: 0018:ffffc9000fa67a40 EFLAGS: 00050287 RAX: ffffffff81e0e7ab RBX: 0000000020001000 RCX: 0000000000040000 RDX: ffffc90004fa1000 RSI: 000000000000007d RDI: 000000000000007e RBP: ffffc9000fa67af8 R08: ffffffff81e0e748 R09: ffffffff84b90999 R10: 0000000000000002 R11: ffff88805c679e00 R12: 000000000000fecc R13: dffffc0000000000 R14: 0000000020010000 R15: 1ffff92001f4cf50 fault_in_iov_iter_readable+0x229/0x280 lib/iov_iter.c:94 generic_perform_write+0x259/0x6d0 mm/filemap.c:4040 shmem_file_write_iter+0xf9/0x120 mm/shmem.c:3221 new_sync_write fs/read_write.c:590 [inline] vfs_write+0xa6d/0xc90 fs/read_write.c:683 ksys_write+0x183/0x2b0 fs/read_write.c:736 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fde8757def9 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:00007fde86fff038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007fde87735f80 RCX: 00007fde8757def9 RDX: 000000000000fecc RSI: 0000000020000100 RDI: 0000000000000003 RBP: 00007fde875f0b76 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fde87735f80 R15: 00007fde8785fa28 ---------------- Code disassembly (best guess): 0: b3 ff mov $0xff,%bl 2: 4c 8d b3 ff 0f 00 00 lea 0xfff(%rbx),%r14 9: 48 89 d8 mov %rbx,%rax c: 4d 01 e6 add %r12,%r14 f: 49 81 e6 00 f0 ff ff and $0xfffffffffffff000,%r14 16: 49 39 c6 cmp %rax,%r14 19: 72 6b jb 0x86 1b: e8 95 cd b3 ff call 0xffb3cdb5 20: 4c 39 f3 cmp %r14,%rbx 23: 74 6e je 0x93 25: 4c 89 64 24 10 mov %r12,0x10(%rsp) * 2a: 44 8a 23 mov (%rbx),%r12b <-- trapping instruction 2d: 43 0f b6 04 2f movzbl (%r15,%r13,1),%eax 32: 84 c0 test %al,%al 34: 75 18 jne 0x4e 36: 44 88 64 24 40 mov %r12b,0x40(%rsp) 3b: 48 rex.W 3c: 81 .byte 0x81 3d: c3 ret 3e: 00 10 add %dl,(%rax) --- 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