[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aRzPqYfXc6mtR1U9@casper.infradead.org>
Date: Tue, 18 Nov 2025 19:57:29 +0000
From: Matthew Wilcox <willy@...radead.org>
To: "Vishal Moola (Oracle)" <vishal.moola@...il.com>
Cc: Biju Das <biju.das.jz@...renesas.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
"hch@...radead.org" <hch@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"urezki@...il.com" <urezki@...il.com>
Subject: Re: [PATCH v3 0/4] make vmalloc gfp flags usage more apparent
On Tue, Nov 18, 2025 at 09:07:56AM -0800, Vishal Moola (Oracle) wrote:
> 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.
I see:
Unexpected gfp: 0x1000000 (__GFP_NOLOCKDEP). Fixing up to gfp: 0x2dc0 (GFP_KERNEL|__GFP_ZERO|__GFP_NOWARN). Fix your code!
I suspect __GFP_NOLOCKDEP should also be permitted by vmalloc.
Powered by blists - more mailing lists