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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C44E5C4332F for ; Mon, 28 Feb 2022 11:06:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234991AbiB1LHC (ORCPT ); Mon, 28 Feb 2022 06:07:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43460 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233476AbiB1LHB (ORCPT ); Mon, 28 Feb 2022 06:07:01 -0500 Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0EBEB6621A for ; Mon, 28 Feb 2022 03:06:23 -0800 (PST) Received: by mail-io1-f71.google.com with SMTP id x16-20020a6bfe10000000b006409f03e39eso8325749ioh.7 for ; Mon, 28 Feb 2022 03:06:23 -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=PgeDyvFRY9sAIVUrNxAGZJTxbk91znpMzjI+AHAgu4RfRYv4DXlgn1judYftBRixSd yjloQBgTQpAYRLsgADZ/yF7ohZOTharl3f168ucdKvbXqK8tkJWSvJzzl12i/Ut4HkcL zTgH0CRR+SZhYYI3t4XwDWkSVvBpoRTMByidTwKXJ6FLJk1B5gHSInf6pCVHD8umO5cF o6L6gLLNrzNvLQ2lDPLOQ97wAtCyhY3tewNLzMTD7yi1onHhfzMsLpZuxPn97VDaLWRp TGdRvJaiAvBrp3heMfRipUKzBV6mpmcZlGrPDbeaXma32KEuGInqgeqKni0ndjAYp6P4 vkHQ== X-Gm-Message-State: AOAM530sfEYGG1GpgBDKmr1lkp1Bz1iw07qfmD3nYYyp0uEryK3nWfaR k8eEMUoSgoxgg+3MF4hzOgAcIU9P68WXIX6Df1K/QmIzKJd8 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" Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org > #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