[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhysqzlMHWTXLR4B@linutronix.de>
Date: Mon, 28 Feb 2022 12:06:19 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: syzbot <syzbot+a526c269335f529d25c8@...kaller.appspotmail.com>,
cgroups@...r.kernel.org, hannes@...xchg.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-next@...r.kernel.org, mhocko@...nel.org,
roman.gushchin@...ux.dev, sfr@...b.auug.org.au,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] linux-next test error: WARNING in
__mod_memcg_lruvec_state
#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
Powered by blists - more mailing lists