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=-5.4 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 96557C433DF for ; Wed, 10 Jun 2020 01:48:18 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 741872076A for ; Wed, 10 Jun 2020 01:48:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726109AbgFJBsR (ORCPT ); Tue, 9 Jun 2020 21:48:17 -0400 Received: from mail-io1-f72.google.com ([209.85.166.72]:49611 "EHLO mail-io1-f72.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725944AbgFJBsP (ORCPT ); Tue, 9 Jun 2020 21:48:15 -0400 Received: by mail-io1-f72.google.com with SMTP id d20so535730iom.16 for ; Tue, 09 Jun 2020 18:48:14 -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=tCNv4MDksUTvEJtckn2siy6hhdfAtvNNzotf7ihGV9M=; b=prlC7RMCKksjlIYZwDYHH9UGuLoGqJU2pqJH6jRoUYgrK6ShKxiug1poP5/DH0LSXN mXUGRrOak+s3RTNFcO89+qWMnwwD17G9W45qSVB3jkU4aV582d+qBgVAUjlgtFhyE277 5o5a2+mRAWpeILYac2qYavzSQwOizUVZnAlPmy1Hin+Z+jSte8Cp5MNRjE7YokhizH4s O31+9eN5fAQUedRN6dTtef512vR56QdQABQQnLc49UMZyFpsA4DH3jT/Uy9HT8Oah/4U KqyUr4rntkOc7XwMIzZFGN054Vx6CsQTigyuFbftBqorW/8wmbtZnS7ry0FrhAJBMO7K YaZA== X-Gm-Message-State: AOAM530Gf8qbD7ijKdN7Dw4j4d7yWFMlFxPC+EmVfsoF5c9I9F1QslVK aiaTGQQ/v+fL0pIakKXPlYe1B0kcuh/l79WN8xOhnXL57R3h X-Google-Smtp-Source: ABdhPJzlbbQqB+bRC/Lpi5Ncz3C53bANqqT4UivwwU48hlv7Ea2cNi/oHmCV7GKnB7uL5/fOrvLrCG+ZyxAfqp0k+QhYJ3u3uZQk MIME-Version: 1.0 X-Received: by 2002:a6b:7516:: with SMTP id l22mr1061993ioh.18.1591753693598; Tue, 09 Jun 2020 18:48:13 -0700 (PDT) Date: Tue, 09 Jun 2020 18:48:13 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <0000000000007a16f705a7b1096d@google.com> Subject: upstream test error: BUG: using smp_processor_id() in preemptible code in ext4_mb_new_blocks From: syzbot To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, tytso@mit.edu Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following crash on: HEAD commit: 5b14671b Merge tag 'fuse-update-5.8' of git://git.kernel.o.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12a11ec1100000 kernel config: https://syzkaller.appspot.com/x/.config?x=d1ea633f7958e008 dashboard link: https://syzkaller.appspot.com/bug?extid=0113b9be6667b5b50840 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+0113b9be6667b5b50840@syzkaller.appspotmail.com BUG: using smp_processor_id() in preemptible [00000000] code: systemd-rfkill/6740 caller is ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711 CPU: 0 PID: 6740 Comm: systemd-rfkill Not tainted 5.7.0-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 lib/smp_processor_id.c:47 [inline] debug_smp_processor_id.cold+0x88/0x9b lib/smp_processor_id.c:57 ext4_mb_new_blocks+0xa77/0x3b30 fs/ext4/mballoc.c:4711 ext4_ext_map_blocks+0x2044/0x3410 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:3641 do_mkdirat+0x21e/0x280 fs/namei.c:3664 do_syscall_64+0xf6/0x7d0 arch/x86/entry/common.c:295 entry_SYSCALL_64_after_hwframe+0x49/0xb3 RIP: 0033:0x7f449ff49687 Code: Bad RIP value. RSP: 002b:00007ffdd3b9fe58 EFLAGS: 00000246 ORIG_RAX: 0000000000000053 RAX: ffffffffffffffda RBX: 00005567752fd985 RCX: 00007f449ff49687 RDX: 00007ffdd3b9fd20 RSI: 00000000000001ed RDI: 00005567752fd985 RBP: 00007f449ff49680 R08: 0000000000000100 R09: 0000000000000000 R10: 00005567752fd980 R11: 0000000000000246 R12: 00000000000001ed R13: 00007ffdd3b9ffe0 R14: 0000000000000000 R15: 0000000000000000 --- 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.