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=-3.7 required=3.0 tests=BAYES_00,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 3D4CFC07E95 for ; Tue, 20 Jul 2021 10:59:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1D78961107 for ; Tue, 20 Jul 2021 10:59:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235423AbhGTKSc (ORCPT ); Tue, 20 Jul 2021 06:18:32 -0400 Received: from mail-il1-f198.google.com ([209.85.166.198]:50690 "EHLO mail-il1-f198.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238009AbhGTKKq (ORCPT ); Tue, 20 Jul 2021 06:10:46 -0400 Received: by mail-il1-f198.google.com with SMTP id w8-20020a056e021c88b02902095727d18dso12880163ill.17 for ; Tue, 20 Jul 2021 03:51:24 -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=Ole8b2cR6lQoDSXLNb5l4NYhygBr3zVA6T0AtIVglTc=; b=VcZ7iF96MchxBwPHXsLAqhgiLRKWZo0lDO7Ybl3JxPjuMGlusjfAnw14dzSSMaFXK/ geLY3EWUBwG9R4lCBb+1R3kFVdafZZkTBwS47Yh7EP50weilVhulLjD5OLyJM0VvbSJh zjTt1vVWraEH+vwBQ0QCOIUXHbV16bHAYOjkUGUhcWTHligH9VNh4DaSHx7IGf4dfTC9 detIhY8MmfHXYkCsmaPMAMzMnlbe1RtwH8/moa8/8pOAwIt3+fzFCeZlOPfuagv50XML Ary5Lq0YsgE6c0Ubu9K6nsbBFAMYOFjve4dJYKYUsNtnzLOtKKHA5T+g58GoManQh67d bEXQ== X-Gm-Message-State: AOAM531Ek35U6XkfVJYxlVFS2RT+brNULeHpsQrMnugihHbp2U0AwkDf 0eothtnL/4608huZcMOjxCqes/K1b8tP34wN7/rJxsLDp3dn X-Google-Smtp-Source: ABdhPJzrg1xbwj9UVISbQgfhQpJ0AXZpQnVvU/gpeRDUY2fKFNkOEYZTFzgFeOOaXAO+KHJa+QEprVV74Yx3q4DnDsSE2p1Jq8k1 MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1a46:: with SMTP id u6mr20003836ilv.135.1626778282613; Tue, 20 Jul 2021 03:51:22 -0700 (PDT) Date: Tue, 20 Jul 2021 03:51:22 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000a9e38905c78bd588@google.com> Subject: [syzbot] linux-next boot error: BUG: sleeping function called from invalid context in cgroup_rstat_flush From: syzbot To: cgroups@vger.kernel.org, hannes@cmpxchg.org, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, lizefan.x@bytedance.com, sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com, tj@kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, syzbot found the following issue on: HEAD commit: 6e235535ce82 Add linux-next specific files for 20210716 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=17f3d7e2300000 kernel config: https://syzkaller.appspot.com/x/.config?x=b07a961928126747 dashboard link: https://syzkaller.appspot.com/bug?extid=0e2d06632863e7ddb1c7 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+0e2d06632863e7ddb1c7@syzkaller.appspotmail.com BUG: sleeping function called from invalid context at kernel/cgroup/rstat.c:200 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 39, name: kworker/u4:3 3 locks held by kworker/u4:3/39: #0: ffff888010869138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: arch_atomic64_set arch/x86/include/asm/atomic64_64.h:34 [inline] #0: ffff888010869138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: atomic64_set include/asm-generic/atomic-instrumented.h:620 [inline] #0: ffff888010869138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: atomic_long_set include/asm-generic/atomic-long.h:41 [inline] #0: ffff888010869138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: set_work_data kernel/workqueue.c:617 [inline] #0: ffff888010869138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: set_work_pool_and_clear_pending kernel/workqueue.c:644 [inline] #0: ffff888010869138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x871/0x1630 kernel/workqueue.c:2247 #1: ffffc90000e2fdb0 (stats_flush_work){+.+.}-{0:0}, at: process_one_work+0x8a5/0x1630 kernel/workqueue.c:2251 #2: ffffffff8bad45d8 (stats_flush_lock){+.+.}-{2:2}, at: spin_trylock include/linux/spinlock.h:369 [inline] #2: ffffffff8bad45d8 (stats_flush_lock){+.+.}-{2:2}, at: mem_cgroup_flush_stats mm/memcontrol.c:5358 [inline] #2: ffffffff8bad45d8 (stats_flush_lock){+.+.}-{2:2}, at: flush_memcg_stats_work+0xd/0x50 mm/memcontrol.c:5373 Preemption disabled at: [<0000000000000000>] 0x0 CPU: 0 PID: 39 Comm: kworker/u4:3 Not tainted 5.14.0-rc1-next-20210716-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events_unbound flush_memcg_stats_work Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:105 ___might_sleep.cold+0x1f3/0x239 kernel/sched/core.c:9182 cgroup_rstat_flush+0x1c/0x50 kernel/cgroup/rstat.c:200 mem_cgroup_flush_stats mm/memcontrol.c:5361 [inline] mem_cgroup_flush_stats mm/memcontrol.c:5356 [inline] flush_memcg_stats_work+0x39/0x50 mm/memcontrol.c:5373 process_one_work+0x98d/0x1630 kernel/workqueue.c:2276 worker_thread+0x658/0x11f0 kernel/workqueue.c:2422 kthread+0x3e5/0x4d0 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 --- 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.