On Mon, Aug 26, 2024 at 10:47:13AM +0200, Michal Hocko wrote: > From: Michal Hocko <mho...@suse.com> > > There is no existing user of the flag and the flag is dangerous because > a nested allocation context can use GFP_NOFAIL which could cause > unexpected failure. Such a code would be hard to maintain because it > could be deeper in the call chain. > > PF_MEMALLOC_NORECLAIM has been added even when it was pointed out [1] > that such a allocation contex is inherently unsafe if the context > doesn't fully control all allocations called from this context.
Wouldn't a straight-up revert of eab0af905bfc be cleaner? Or is there a reason to keep PF_MEMALLOC_NOWARN?