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 B36C5C433DF for ; Tue, 2 Jun 2020 11:20:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9658320679 for ; Tue, 2 Jun 2020 11:20:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726461AbgFBLUY (ORCPT ); Tue, 2 Jun 2020 07:20:24 -0400 Received: from mail-il1-f198.google.com ([209.85.166.198]:45721 "EHLO mail-il1-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726012AbgFBLUT (ORCPT ); Tue, 2 Jun 2020 07:20:19 -0400 Received: by mail-il1-f198.google.com with SMTP id q24so11394877ili.12 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=By/yreSs9OawvTt2wVwQ1TPEtrrHeBTj3KKjcSSBhe4=; b=R8sxNpxZyVODpg7MSxDV0h+y5KbsUm03djGYF72j5zdZF0oUFn/rIrajr+5j8VNTrA FmzOjbNcfiZrNbAXVXRXLGtswsH3kHEg9KSyW7eeWalCr4AGxXHDwQD3ZzAQkfhhKI13 E5OgE6XLlFaDaFh+03QEwvwhKb69AvxWHmRm79VZgbRGI2rH+D5NilZ1EVC2w9qbIKyN pfimpL99Zad5VWwTVHW3gZ7utmQtf5HbGa8JzwNFF+WZqv7fqion60q/2LU5kqhpjt7S WrY/j6ML3ryrwVnk6DYuZB0hkYVTk8mVjfeRWN2bUsjE6gA38LASbjCOYmhxv3W2fn1y 56bg== X-Gm-Message-State: AOAM532g3CZnE1+siJuTNeDKVYpRHBquuwXCEEBUsgI4j1Kentq7okfK nw51fdnPqGBLba0n/FObX/rAVZAzXpz0F4Y6T275iaFL4lbi X-Google-Smtp-Source: ABdhPJxdjR1/A/OQRWFqkFOdbGjxot/+llfg+gW20CifX8hdRi7XJ9VktHEtCbIgum9wtVH3pDT0wuX5bHZmgnyov8lEbUPqWAxi MIME-Version: 1.0 X-Received: by 2002:a92:c048:: with SMTP id o8mr1367326ilf.202.1591096816969; 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: <00000000000094436005a7181833@google.com> Subject: linux-next test error: BUG: using smp_processor_id() in preemptible [ADDR] code: kworker/u4:LINE/46 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-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: 0e21d462 Add linux-next specific files for 20200602 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=17fee516100000 kernel config: https://syzkaller.appspot.com/x/.config?x=ecc1aef35f550ee3 dashboard link: https://syzkaller.appspot.com/bug?extid=4d28f1825b8fb92fa383 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+4d28f1825b8fb92fa383@syzkaller.appspotmail.com BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u4:3/46 caller is ext4_mb_new_blocks+0xa4d/0x3b70 fs/ext4/mballoc.c:4711 CPU: 1 PID: 46 Comm: kworker/u4:3 Not tainted 5.7.0-next-20200602-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: writeback wb_workfn (flush-8:0) 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 mpage_map_one_extent fs/ext4/inode.c:2377 [inline] mpage_map_and_submit_extent fs/ext4/inode.c:2430 [inline] ext4_writepages+0x1ab5/0x3400 fs/ext4/inode.c:2782 do_writepages+0xfa/0x2a0 mm/page-writeback.c:2338 __writeback_single_inode+0x12a/0x13d0 fs/fs-writeback.c:1453 writeback_sb_inodes+0x515/0xdc0 fs/fs-writeback.c:1717 __writeback_inodes_wb+0xc3/0x250 fs/fs-writeback.c:1786 wb_writeback+0x8db/0xd50 fs/fs-writeback.c:1895 wb_check_old_data_flush fs/fs-writeback.c:1997 [inline] wb_do_writeback fs/fs-writeback.c:2050 [inline] wb_workfn+0xab3/0x1090 fs/fs-writeback.c:2079 process_one_work+0x965/0x1690 kernel/workqueue.c:2269 worker_thread+0x96/0xe10 kernel/workqueue.c:2415 kthread+0x3b5/0x4a0 kernel/kthread.c:291 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 tipc: TX() has been purged, node left! --- 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.