linux-kernel - Re: [syzbot] linux-next test error: WARNING in __mod_memcg_lruvec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <000000000000e3387805d912097c@google.com>
Date:   Mon, 28 Feb 2022 03:06:22 -0800
From:   syzbot <syzbot+a526c269335f529d25c8@...kaller.appspotmail.com>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     akpm@...ux-foundation.org, bigeasy@...utronix.de,
        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

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