From: Sebastian Andrzej Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: syzbot
<syzbot+a526c269335f529d25c8-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org,
sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state
Date: Mon, 28 Feb 2022 12:06:19 +0100 [thread overview]
Message-ID: <YhysqzlMHWTXLR4B@linutronix.de> (raw)
In-Reply-To: <20220227220943.490fb7b5f7c57d872f9523cb-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
#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
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: syzbot <syzbot+a526c269335f529d25c8@syzkaller.appspotmail.com>,
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 12:06:19 +0100 [thread overview]
Message-ID: <YhysqzlMHWTXLR4B@linutronix.de> (raw)
In-Reply-To: <20220227220943.490fb7b5f7c57d872f9523cb@linux-foundation.org>
#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
next prev parent reply other threads:[~2022-02-28 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 7:23 [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec_state syzbot
2022-02-26 7:23 ` syzbot
[not found] ` <000000000000c7fde605d8e6b085-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-02-28 6:09 ` Andrew Morton
2022-02-28 6:09 ` Andrew Morton
[not found] ` <20220227220943.490fb7b5f7c57d872f9523cb-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2022-02-28 11:06 ` Sebastian Andrzej Siewior [this message]
2022-02-28 11:06 ` Sebastian Andrzej Siewior
[not found] ` <YhysqzlMHWTXLR4B-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2022-02-28 11:06 ` syzbot
2022-02-28 11:06 ` syzbot
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=YhysqzlMHWTXLR4B@linutronix.de \
--to=bigeasy-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
--cc=syzbot+a526c269335f529d25c8-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.