From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Misbah Anjum N <misanjum@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-next@vger.kernel.org
Subject: Re: [REGRESSION] [next-20251117] ppc64le: WARNING in vmalloc_fix_flags with __GFP_ACCOUNT in BPF/seccomp path
Date: Tue, 18 Nov 2025 13:21:24 +0530 [thread overview]
Message-ID: <87bjkz3hj7.ritesh.list@gmail.com> (raw)
In-Reply-To: <dbe42ce9543dbc3af95f95d6a6d9540b@linux.ibm.com>
Misbah Anjum N <misanjum@linux.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
prev parent reply other threads:[~2025-11-18 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 4:42 Misbah Anjum N
2025-11-18 7:51 ` Ritesh Harjani [this message]
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=87bjkz3hj7.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=misanjum@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox