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 X-Spam-Level: X-Spam-Status: No, score=-0.4 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D523FC433E1 for ; Tue, 2 Jun 2020 11:20:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BE71120679 for ; Tue, 2 Jun 2020 11:20:28 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726580AbgFBLU2 (ORCPT ); Tue, 2 Jun 2020 07:20:28 -0400 Received: from mail-il1-f199.google.com ([209.85.166.199]:32960 "EHLO mail-il1-f199.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725969AbgFBLUS (ORCPT ); Tue, 2 Jun 2020 07:20:18 -0400 Received: by mail-il1-f199.google.com with SMTP id c11so7843133ilq.0 for ; Tue, 02 Jun 2020 04:20:17 -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=zMicM0NHbCSTRWS4r82QF2SXzu5Q7H29IEKe/4Smvew=; b=QybZFWCVScci8VTeKCoQubAgpthZcGXk+iKj6L4MuissQsXD2Wn1bcQcuJBt8tjdqq 4N25FpyuRi6lzObv88L73YenM1Y89UtxI5ETTUCR/mOi+vdyywKl/uI3CZzi4L0XM7NO GumZsaLuS/x+w7pearF9aXAQeNgN+U4lLWOHe7rxv5ioweuzyhKm0GThnx+33/+uwx04 1s9m6Huqy//jL5Wrw0NUwJN3Hiwt6EMqpLTGsshxzRg8kDxrzjc8WJmFu2JyJSGGZg6V Xb+Blcu/zh3jJHFVru2+1zEQ/aLYpsBRanMbakXFe7wrqqn2bcUOu9tdko5njNmw58GH e61w== X-Gm-Message-State: AOAM5312++ATovO+nC0T0tlsMUneli5MsfPxZn4eo/H4KkyqeWIwSMdF Ebrao8HqWndBVM+heiYwLAPnRbrLe+KjVPft4+HqZ6SFXaUA X-Google-Smtp-Source: ABdhPJwd5/P+dkeerOSL4vtqpDMgbEz3TJ/gVhSpiVhzNtZKOPYyEBX9SOJi9pOTo8GI4a9Hf94RBj8rRJsT5JMG09Hx74jWrJFC MIME-Version: 1.0 X-Received: by 2002:a05:6638:101c:: with SMTP id r28mr26033924jab.84.1591096816692; Tue, 02 Jun 2020 04:20:16 -0700 (PDT) Date: Tue, 02 Jun 2020 04:20:16 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000008ff8ea05a71818b5@google.com> Subject: linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: syz-fuzzer/6792 From: syzbot To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Hello, syzbot found the following crash on: HEAD commit: 0e21d462 Add linux-next specific files for 20200602 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=127233ee100000 kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3 dashboard link: https://syzkaller.appspot.com/bug?extid=82f324bb69744c5f6969 compiler: gcc (GCC) 9.0.0 20181231 (experimental) IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+82f324bb69744c5f6969@syzkaller.appspotmail.com BUG: using smp_processor_id() in preemptible [00000000] code: syz-fuzzer/6792 caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711 CPU: 1 PID: 6792 Comm: syz-fuzzer Not tainted 5.7.0-next-20200602-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x18f/0x20d lib/dump_stack.c:118 check_preemption_disabled+0x20d/0x220 lib/smp_processor_id.c:48 ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711 ext4_ext_map_blocks+0x201b/0x33e0 fs/ext4/extents.c:4244 ext4_map_blocks+0x4cb/0x1640 fs/ext4/inode.c:626 ext4_getblk+0xad/0x520 fs/ext4/inode.c:833 ext4_bread+0x7c/0x380 fs/ext4/inode.c:883 ext4_append+0x153/0x360 fs/ext4/namei.c:67 ext4_init_new_dir fs/ext4/namei.c:2757 [inline] ext4_mkdir+0x5e0/0xdf0 fs/ext4/namei.c:2802 vfs_mkdir+0x419/0x690 fs/namei.c:3632 do_mkdirat+0x21e/0x280 fs/namei.c:3655 do_syscall_64+0x60/0xe0 arch/x86/entry/common.c:359 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x4b02a0 Code: Bad RIP value. RSP: 002b:000000c00010d4b8 EFLAGS: 00000212 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 000000c00002c000 RCX: 00000000004b02a0 RDX: 00000000000001c0 RSI: 000000c000026b40 RDI: ffffffffffffff9c RBP: 000000c00010d510 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000212 R12: ffffffffffffffff R13: 000000000000005b R14: 000000000000005a R15: 0000000000000100 --- This bug 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 bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.