| 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
| ||
|
Message-ID: <87bjkz3hj7.ritesh.list@gmail.com> Date: Tue, 18 Nov 2025 13:21:24 +0530 From: Ritesh Harjani (IBM) <ritesh.list@...il.com> To: Misbah Anjum N <misanjum@...ux.ibm.com> Cc: linux-kernel@...r.kernel.org, bpf@...r.kernel.org, linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org, linux-next@...r.kernel.org Subject: Re: [REGRESSION] [next-20251117] ppc64le: WARNING in vmalloc_fix_flags with __GFP_ACCOUNT in BPF/seccomp path Misbah Anjum N <misanjum@...ux.ibm.com> writes: > Hi, > > I'm reporting a regression in linux-next that was introduced between > 20251114 and 20251117. > > Regression Info: > - Working: 6.18.0-rc5-next-20251114 > - Broken: 6.18.0-rc6-next-20251117 > > Environment: > - IBM Power11 pSeries (ppc64le) > - Fedora43 Distro > > Issue: > WARNING: mm/vmalloc.c:3937 at vmalloc_fix_flags+0x6c/0xa0 > "Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to gfp: 0xdc0 > (GFP_KERNEL|__GFP_ZERO). Fix your code!" > > Call Trace: > [ 523.921345] Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to > gfp: 0xdc0 (GFP_KERNEL|__GFP_ZERO). Fix your code! > [ 523.921356] WARNING: mm/vmalloc.c:3937 at > vmalloc_fix_flags+0x6c/0xa0, CPU#69: (ostnamed)/6500 This was reported here too - https://lore.kernel.org/all/69158bb1.a70a0220.3124cb.001e.GAE@google.com/ Looks like it should be fixed with v3, which was posted just yesterday... https://lore.kernel.org/all/20251117173530.43293-2-vishal.moola@gmail.com/ So, I guess, latest linux-next should not show this warning on ppc64le either. -ritesh
Powered by blists - more mailing lists