From: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"hch@infradead.org" <hch@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"urezki@gmail.com" <urezki@gmail.com>
Subject: Re: [PATCH v3 0/4] make vmalloc gfp flags usage more apparent
Date: Tue, 18 Nov 2025 09:07:56 -0800 [thread overview]
Message-ID: <aRyn7Ibaqa5rlHHx@fedora> (raw)
In-Reply-To: <TY3PR01MB11346E8536B69E11A9A9DAB0886D6A@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On Tue, Nov 18, 2025 at 04:14:01PM +0000, Biju Das wrote:
> Hi All,
>
> I get below warning with today's next. Can you please suggest how to fix this warning?
Thanks Biju. This has been fixed and will be in whenever Andrews tree
gets merged again.
>
> [ 13.122280] systemd[1]: File System Check on Root Device was skipped because of an unmet condition check (ConditionPathIsReadWrite=!/).
> [ 13.142562] ------------[ cut here ]------------
> [ 13.147308] Unexpected gfp: 0x400000 (__GFP_ACCOUNT). Fixing up to gfp: 0x100dc0 (GFP_USER|__GFP_ZERO). Fix your code!
> [ 13.158526] WARNING: mm/vmalloc.c:3937 at vmalloc_fix_flags+0x9c/0xac, CPU#1: systemd/1
> [ 13.166576] Modules linked in: backlight ipv6
> [ 13.170983] CPU: 1 UID: 0 PID: 1 Comm: systemd Not tainted 6.18.0-rc6-next-20251118-gcc318393a5df #175 PREEMPT
> [ 13.181082] Hardware name: Renesas SMARC EVK based on r9a07g054l2 (DT)
> [ 13.187641] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> [ 13.194675] pc : vmalloc_fix_flags+0x9c/0xac
> [ 13.194705] lr : vmalloc_fix_flags+0x9c/0xac
> [ 13.194715] sp : ffff8000828fbab0
> [ 13.194719] x29: ffff8000828fbad0 x28: 0000000000000000 x27: 0000000000000000
> [ 13.194734] x26: 0000000000000000 x25: 0000000000000000 x24: 000000000000000f
> [ 13.194746] x23: 0000ffffcc595b58 x22: 0000000000001000 x21: 0000000000100cc0
> [ 13.194757] x20: ffff8000801d7af0 x19: 0000000000001000 x18: 0000000000000006
> [ 13.194768] x17: 0000000000000000 x16: 0000000000000000 x15: 006c326703000000
> [ 13.194779] x14: 00000000000001da x13: 00000000000001da x12: 0000000000000000
> [ 13.194790] x11: 00000000000000c0 x10: 0000000000000ac0 x9 : ffff8000828fb920
> [ 13.194802] x8 : ffff00000aca8b20 x7 : 00000000021cb08a x6 : 0000000000000186
> [ 13.194813] x5 : 000000009d17f2f7 x4 : ffff800037e00000 x3 : 0000000000000010
> [ 13.194824] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff00000aca8000
> [ 13.194836] Call trace:
> [ 13.194842] vmalloc_fix_flags+0x9c/0xac (P)
> [ 13.194855] __vmalloc_noprof+0x60/0x74
> [ 13.194865] bpf_prog_alloc_no_stats+0x44/0x218
> [ 13.194879] bpf_prog_alloc+0x28/0xec
> [ 13.194888] bpf_prog_load+0x168/0xcdc
> [ 13.194899] __sys_bpf+0x814/0x211c
> [ 13.194907] __arm64_sys_bpf+0x24/0x40
> [ 13.194916] invoke_syscall+0x48/0x104
> [ 13.194927] el0_svc_common.constprop.0+0x40/0xe0
> [ 13.194935] do_el0_svc+0x1c/0x28
> [ 13.194943] el0_svc+0x34/0x108
> [ 13.194955] el0t_64_sync_handler+0xa0/0xf0
> [ 13.194964] el0t_64_sync+0x198/0x19c
> [ 13.194975] ---[ end trace 0000000000000000 ]---
> [ 13.328233] fuse: init (API version 7.45)
> [ 13.339395] systemd[1]: Starting Journal Service...
>
>
> Cheers,
> Biju
next prev parent reply other threads:[~2025-11-18 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 16:14 Biju Das
2025-11-18 17:07 ` Vishal Moola (Oracle) [this message]
2025-11-18 19:57 ` Matthew Wilcox
2025-11-19 18:55 ` Vishal Moola (Oracle)
2025-11-21 7:29 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2025-11-17 17:35 Vishal Moola (Oracle)
2025-11-20 1:03 ` SeongJae Park
2025-11-20 18:04 ` Andrew Morton
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=aRyn7Ibaqa5rlHHx@fedora \
--to=vishal.moola@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=bpf@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=urezki@gmail.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