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 1B80CC433F5 for ; Mon, 28 Feb 2022 11:06:25 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1EFE28D0001; Mon, 28 Feb 2022 06:06:24 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 188058D0006; Mon, 28 Feb 2022 06:06:24 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id F168D8D0001; Mon, 28 Feb 2022 06:06:23 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0128.hostedemail.com [216.40.44.128]) by kanga.kvack.org (Postfix) with ESMTP id DA0028D0001 for ; Mon, 28 Feb 2022 06:06:23 -0500 (EST) Received: from smtpin30.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 99CBA9C15A for ; Mon, 28 Feb 2022 11:06:23 +0000 (UTC) X-FDA: 79191909846.30.6A2C2D0 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by imf31.hostedemail.com (Postfix) with ESMTP id 0E90B2000A for ; Mon, 28 Feb 2022 11:06:22 +0000 (UTC) Date: Mon, 28 Feb 2022 12:06:19 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1646046380; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=kuYSAt1MZUM/puwk3yZe7khsCEtHcjgvevbbDPW87Zk=; b=LhXrKps5NOhICMcZKstR1+jE06JIFDHGjkMlKSATJoZgFQyZ8pK2n5VWwZri6sGMljWH9g 6WLE0k08QFMolOr516NBCQZ3vGUTVimY6xVTLdEBJfTOf3VGOPv7gAxHMMCyqYysM97V8+ 18+EXOf5bzfsoi9/qExuIC+mncp8HDV30K23ZwWHfDtnjmRQaEHjcBAH+8cCHOcP2MtfLz W6DFUWJjy97Y+hOwOPzo9IyuYGt/GXbD9CYsWZkHYTED/5c+aRyYszrRFpxO+nUkwD5RLq Ic2vobdPqB8lalkJ6UbsRkbK8vqOFoTLuQTiwxvJXmZ0RqFKM266ujgKTUYCrw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1646046380; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=kuYSAt1MZUM/puwk3yZe7khsCEtHcjgvevbbDPW87Zk=; b=iBu5w7qyoK/y+oosN2Cvtf8iwCsNS0eYQ8x4WLqriihNBzWDKhtLPmKfRL/IkcMYx1cZ4G vqvOGjGC4TnBxNAA== From: Sebastian Andrzej Siewior To: Andrew Morton Cc: syzbot , 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 Subject: Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state Message-ID: References: <000000000000c7fde605d8e6b085@google.com> <20220227220943.490fb7b5f7c57d872f9523cb@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220227220943.490fb7b5f7c57d872f9523cb@linux-foundation.org> X-Rspamd-Queue-Id: 0E90B2000A X-Stat-Signature: cyfxoxadpndcuwe5rh7eptjz6ambj69k Authentication-Results: imf31.hostedemail.com; dkim=pass header.d=linutronix.de header.s=2020 header.b=LhXrKps5; dkim=pass header.d=linutronix.de header.s=2020e header.b=iBu5w7qy; spf=pass (imf31.hostedemail.com: domain of bigeasy@linutronix.de designates 193.142.43.55 as permitted sender) smtp.mailfrom=bigeasy@linutronix.de; dmarc=pass (policy=none) header.from=linutronix.de X-Rspam-User: X-Rspamd-Server: rspam08 X-HE-Tag: 1646046382-176315 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 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