Re: [PATCH v3 0/4] make vmalloc gfp flags usage more apparent

Next message: Mike Christie: "Re: [PATCH] scsi: target: reset t_task_cdb pointer in error case"
Previous message: Steven Rostedt: "Re: Clarifying confusion of our variable placement rules caused by cleanup.h"
In reply to: Vishal Moola (Oracle): "Re: [PATCH v3 0/4] make vmalloc gfp flags usage more apparent"
Next in thread: Vishal Moola (Oracle): "Re: [PATCH v3 0/4] make vmalloc gfp flags usage more apparent"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Matthew Wilcox

Date: Tue Nov 18 2025 - 14:57:33 EST

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.