linux-kernel - Re: [syzbot] [cgroups?] [mm?] 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] [thread-next>] [day] [month] [year] [list]

Date: Sat, 13 Apr 2024 21:43:57 -0700
From: Shakeel Butt <shakeel.butt@...ux.dev>
To: Yosry Ahmed <yosryahmed@...gle.com>
Cc: Yu Zhao <yuzhao@...gle.com>, Andrew Morton <akpm@...ux-foundation.org>, 
	syzbot <syzbot+9319a4268a640e26b72b@...kaller.appspotmail.com>, cgroups@...r.kernel.org, hannes@...xchg.org, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, mhocko@...nel.org, muchun.song@...ux.dev, 
	roman.gushchin@...ux.dev, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [cgroups?] [mm?] WARNING in __mod_memcg_lruvec_state

On Thu, Apr 04, 2024 at 09:47:34PM -0700, Yosry Ahmed wrote:
[...]
> >
> > Probably an RT build where _irqsave doesn't disable IRQ?
> 
> Yeah, that's possible. I don't have enough familiarity with RT to know
> for sure. Perhaps lruvec->lru_lock needs to be changed to a
> raw_spinlock_t? I am not sure if that's the correct course of action.

The kernel config does not have CONFIG_PREEMPT_RT enabled. However I
have not idea how irqs are getting enabled to raise this warning.