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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65268C433EF for ; Mon, 28 Feb 2022 11:06:24 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F17CB8D0003; Mon, 28 Feb 2022 06:06:23 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EC7F58D0005; Mon, 28 Feb 2022 06:06:23 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D68BA8D0003; Mon, 28 Feb 2022 06:06:23 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.27]) by kanga.kvack.org (Postfix) with ESMTP id C9EF98D0001 for ; Mon, 28 Feb 2022 06:06:23 -0500 (EST) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id A1A292127D for ; Mon, 28 Feb 2022 11:06:23 +0000 (UTC) X-FDA: 79191909846.02.F7C5AA6 Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) by imf16.hostedemail.com (Postfix) with ESMTP id 1512F18000D for ; Mon, 28 Feb 2022 11:06:22 +0000 (UTC) Received: by mail-io1-f70.google.com with SMTP id g16-20020a05660203d000b005f7b3b0642eso8288201iov.16 for ; Mon, 28 Feb 2022 03:06:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:date:in-reply-to:message-id:subject :from:to:cc; bh=NGeRMKnns/CkUBI5ujUz37hjPuAcdJGxEeUdErwvJTg=; b=I+RtQqaZJKTotP9D1q3augTn631Wrw4SOzlGjPrhyVn0sPmUJsEB53rZodgbzt7Zc7 6QpTba9sBbNhytU9OqJDIuFxXyvHxp0wv6Vi1/8XgjG4bK8k1YJo10tvHPGNkBM4KdMA ajQ1uolLqlNt3XpDyHsNAgvv1w/GpHg3FHp6qGfy6SUlzVJv8t1BoxALG3i7Zqg/2OvD 1mqyIZaUUToVTgHL0Fab6niT+KaC90S+AlXPZX88Cg0mZcjWW9+Dr/DngolyW6imixu1 ma81Iw6mMTGCONFNjT7cCqoQK275xGvX8EVYKy9rLHu+02DXaWQZfvjaTjcpOIcIgIPQ CuRQ== X-Gm-Message-State: AOAM533iTZJldZzUKLI0pAMcvv1K5DIilmbGOqV/Lq+quTPE2XUbqzBi td6mpSmi2Ra8O+byPuhXjlfXOufKVNwkv2uDojL22GIc+amJ X-Google-Smtp-Source: ABdhPJxeTFVWqRcnYQKyeoUA5fs9iql/0PWMeiaUOHnhz5OQep44nI/xLdBW0DeoycNoFKhdyFNXJ09Y+uZkA9tshqS68Y5B1qpt MIME-Version: 1.0 X-Received: by 2002:a02:b19e:0:b0:30d:d9f5:d03c with SMTP id t30-20020a02b19e000000b0030dd9f5d03cmr16825134jah.19.1646046382076; Mon, 28 Feb 2022 03:06:22 -0800 (PST) Date: Mon, 28 Feb 2022 03:06:22 -0800 In-Reply-To: X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000e3387805d912097c@google.com> Subject: Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state From: syzbot To: Sebastian Andrzej Siewior Cc: akpm@linux-foundation.org, bigeasy@linutronix.de, cgroups@vger.kernel.org, hannes@cmpxchg.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@kernel.org, roman.gushchin@linux.dev, sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 1512F18000D X-Stat-Signature: efwm3bgjo7abf1h87guo38crqft8gysr X-Rspam-User: Authentication-Results: imf16.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=appspotmail.com (policy=none); spf=pass (imf16.hostedemail.com: domain of 3rqwcYgkbAJEDJK5v66zCvAA3y.19916zFDzCx98Ez8E.x97@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com designates 209.85.166.70 as permitted sender) smtp.mailfrom=3rqwcYgkbAJEDJK5v66zCvAA3y.19916zFDzCx98Ez8E.x97@M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com X-Rspamd-Server: rspam03 X-HE-Tag: 1646046382-336571 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: > #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/bigeasy/staging.git 71d365035711aef4c4b1018d02fcf7868e3cb0c5 This crash does not have a reproducer. I cannot test it. > > On 2022-02-27 22:09:43 [-0800], Andrew Morton wrote: >> (cc bigeasy) >> >> WARN_ON_ONCE(!irqs_disabled()); >> >> in __mod_memcg_lruvec_state(), methinks. > > This report ist from before you added > mm-memcg-protect-per-cpu-counter-by-disabling-preemption-on-preempt_rt-where-needed-fix.patch > > to your tree. So it can be ignored. The next -next tree should be fine. > > Sebastian