linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+a526c269335f529d25c8@syzkaller.appspotmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
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
Subject: Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
Date: Mon, 28 Feb 2022 03:06:22 -0800	[thread overview]
Message-ID: <000000000000e3387805d912097c@google.com> (raw)
In-Reply-To: <YhysqzlMHWTXLR4B@linutronix.de>

> #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


      reply	other threads:[~2022-02-28 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26  7:23 syzbot
2022-02-28  6:09 ` Andrew Morton
2022-02-28 11:06   ` Sebastian Andrzej Siewior
2022-02-28 11:06     ` syzbot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=000000000000e3387805d912097c@google.com \
    --to=syzbot+a526c269335f529d25c8@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=roman.gushchin@linux.dev \
    --cc=sfr@canb.auug.org.au \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox