Received: by 10.213.65.68 with SMTP id h4csp1398261imn; Wed, 4 Apr 2018 19:03:23 -0700 (PDT) X-Google-Smtp-Source: AIpwx4/NghU5SBAnJhvacy5UzRgzru6gUdhzHxSs8P4QiFE8SfCSyNrYV64QBpIpw/+s+kOUKO/J X-Received: by 2002:a17:902:2d24:: with SMTP id o33-v6mr21344520plb.143.1522893803120; Wed, 04 Apr 2018 19:03:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522893803; cv=none; d=google.com; s=arc-20160816; b=NTbye1Lx8zKF6nZxZDm2Dg1Q3DpH8SiOsxEvGvqncexLuhe7pr/+jqOFMPBPd+ZjWA VgWGSEF1LkkAujhuNN/K459L3oYrpVagNJGl1BjQOPsc63Q7broujaKVrvqlRMukyWWC CYvSCmJLKLQv0pUSGaMsTaZiwf0w5RMkErQG+TWK9s0msv4EG3vAS1UibfKfS9DkisJH nVhdy9G5wJJEUezQZcsOAsaHQ+Iwgqn6JBrIYGuebSdlHF9HSwyoFllXUs7yCIPAKxfj uk6R/kZIRRYvDsP6keis1YoExPUOICKKZAQm0AZuRcCKPdDkcwbRJb6gfhMV7x4TfmUw ju8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:from:subject:message-id:date :mime-version:arc-authentication-results; bh=IWt6mB9Kg3zleiD/vHl4PS3zMBKnDJQcUFZMFpnb+ds=; b=i1MS0db9mIpJ5gSn5B7WPM1rD14IzFI0sfBGKZZRAZ+0Omo/bpR5IQw3Nd8o0wbgnH SiM426fF/w6yUAXzorIExplXqM8ic8xorhIe0QuaBr45Z2RKP/euUpy2CPv4M3WirOnX ycds9SkB9Qo18kq7iydWBpg6pIyUl1H1hlSSCV6LMKsHRuIAsd34xvmRr+PE6ocV0y7Z I6X2LAmzhJOIMCEH2Q0orCP1zjy0gKHN/XIOW2Bf7yugkiMfez5xccTBjmA83JFf+in+ lGvvf+Qkf3EUAM7FXIsKfKC4+w3ccV0Iw7mph7/Go9Jg52EWqZxH2S7qSrEK+s85OWSy VOKg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g8-v6si5196819plm.120.2018.04.04.19.03.09; Wed, 04 Apr 2018 19:03:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=appspotmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752847AbeDECCF (ORCPT + 99 others); Wed, 4 Apr 2018 22:02:05 -0400 Received: from mail-io0-f198.google.com ([209.85.223.198]:39916 "EHLO mail-io0-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752677AbeDECCC (ORCPT ); Wed, 4 Apr 2018 22:02:02 -0400 Received: by mail-io0-f198.google.com with SMTP id e68so14043481iod.6 for ; Wed, 04 Apr 2018 19:02:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=IWt6mB9Kg3zleiD/vHl4PS3zMBKnDJQcUFZMFpnb+ds=; b=VzkTMsjOfUDym3qKtMX6KXtHLnpgem/OJs1dD2mWLe2vhyBqo71hze1RDi7Q72My2C GmAGzwx1BbEkeQ+GEHORHjmOqCQEcEZHSFD0pgXYRM7/l/uaA7anOaSKbHwxBqZFMXZC oJt1ZbqjipGImIoe4mToizcZSOqtH+I5aY0klQpB/PmyFsal6AIetCxB8yOb0yTYVIGb wtG266DO1vXu8QBsX2v+A+aAQAaVmOBdIe1a3eXBEwi7nzKP197OsMISC+LZCB/uC0nE zBA71+F536cZHEnURByZ0g33AY1j+e1CTAjesPh7DYOS+JR1fmlY5ft6f7VvvXtX/phg /Bxw== X-Gm-Message-State: AElRT7FwRa/fwMar5z/KPokqGOh40mQYiXN4GxPfJj3uFyh6Z7eE7Kn3 qVV7Dk7VX94n+23HPfny47EEmKCCGV5k07uHVpm2H1WpoKoT MIME-Version: 1.0 X-Received: by 10.107.174.226 with SMTP id n95mr9608185ioo.124.1522893721918; Wed, 04 Apr 2018 19:02:01 -0700 (PDT) Date: Wed, 04 Apr 2018 19:02:01 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <001a114467485371b605691053fc@google.com> Subject: general protection fault in mount_fs From: syzbot To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot hit the following crash on upstream commit 3e968c9f1401088abc9a19ae6ff571644d37a355 (Wed Apr 4 21:19:24 2018 +0000) Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 syzbot dashboard link: https://syzkaller.appspot.com/bug?extid=01ffaf5d9568dd1609f7 C reproducer: https://syzkaller.appspot.com/x/repro.c?id=6269272955289600 syzkaller reproducer: https://syzkaller.appspot.com/x/repro.syz?id=5190169938362368 Raw console output: https://syzkaller.appspot.com/x/log.txt?id=5077254979715072 Kernel config: https://syzkaller.appspot.com/x/.config?id=9118669095563550941 compiler: gcc (GCC) 7.1.1 20170620 IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+01ffaf5d9568dd1609f7@syzkaller.appspotmail.com It will help syzbot understand when the bug is fixed. See footer for details. If you forward the report, please keep this part and the footer. hfsplus: failed to load root directory hfsplus: failed to load root directory hfsplus: failed to load root directory kasan: CONFIG_KASAN_INLINE enabled kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: 0000 [#1] SMP KASAN Dumping ftrace buffer: (ftrace buffer empty) Modules linked in: CPU: 1 PID: 5704 Comm: syzkaller335224 Not tainted 4.16.0+ #15 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:mount_fs+0x92/0x2d0 fs/super.c:1227 RSP: 0018:ffff8801acc9fad0 EFLAGS: 00010202 RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff81b2ddaa RDX: 0000000000000019 RSI: 0000000000000000 RDI: 00000000000000c8 RBP: ffff8801acc9fb00 R08: 1ffff10035993e87 R09: ffffed0035993efc R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff886b29c0 R13: ffff8801c6243000 R14: ffff8801ac942ac0 R15: 0000000000000000 FS: 00007f8ca5272700(0000) GS:ffff8801db100000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000004c5198 CR3: 00000001af14e000 CR4: 00000000001406e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: vfs_kern_mount.part.26+0xc6/0x4a0 fs/namespace.c:1037 vfs_kern_mount fs/namespace.c:2514 [inline] do_new_mount fs/namespace.c:2517 [inline] do_mount+0xea4/0x2b90 fs/namespace.c:2847 ksys_mount+0xab/0x120 fs/namespace.c:3063 SYSC_mount fs/namespace.c:3077 [inline] SyS_mount+0x39/0x50 fs/namespace.c:3074 do_syscall_64+0x281/0x940 arch/x86/entry/common.c:287 entry_SYSCALL_64_after_hwframe+0x42/0xb7 RIP: 0033:0x44a34a RSP: 002b:00007f8ca5271d38 EFLAGS: 00000297 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000020000318 RCX: 000000000044a34a RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f8ca5271d50 RBP: 00000000006e39c4 R08: 0000000020000140 R09: 000000000000000a R10: 0000000000000000 R11: 0000000000000297 R12: 0000000000000003 R13: 0000000000000004 R14: 00000000006e39c0 R15: 0073756c70736668 Code: 3d 00 f0 ff ff 48 89 c3 0f 87 eb 01 00 00 e8 66 c6 be ff 48 8d bb c8 00 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 08 02 00 00 4c 8b b3 c8 00 00 00 4d 85 f6 0f RIP: mount_fs+0x92/0x2d0 fs/super.c:1227 RSP: ffff8801acc9fad0 ---[ end trace 81f30bb7bca06fe8 ]--- Kernel panic - not syncing: Fatal exception Dumping ftrace buffer: (ftrace buffer empty) Kernel Offset: disabled Rebooting in 86400 seconds.. --- This bug is generated by a dumb bot. It may contain errors. See https://goo.gl/tpsmEJ for details. Direct all questions to syzkaller@googlegroups.com. syzbot will keep track of this bug report. If you forgot to add the Reported-by tag, once the fix for this bug is merged into any tree, please reply to this email with: #syz fix: exact-commit-title If you want to test a patch for this bug, please reply with: #syz test: git://repo/address.git branch and provide the patch inline or as an attachment. To mark this as a duplicate of another syzbot report, please reply with: #syz dup: exact-subject-of-another-report If it's a one-off invalid bug report, please reply with: #syz invalid Note: if the crash happens again, it will cause creation of a new bug report. Note: all commands must start from beginning of the line in the email body.