On Thu, Oct 31, 2019 at 11:43 AM Tejun Heo <tj@xxxxxxxxxx> wrote: > > Hello, > > On Thu, Oct 31, 2019 at 11:30:57AM -0700, Shakeel Butt wrote: > > Basically what I wanted to say that MM treats PF_MEMALLOC as the > > reclaim context while __GFP_MEMALLOC just tells to give access to the > > reserves. As gfpflags_allow_blocking() can be used beyond net > > subsystem, my only concern is its potential usage under PF_MEMALLOC > > context but without __GFP_MEMALLOC. > > Yeah, PF_MEMALLOC is likely the better condition to check here as we > primarily want to know whether %current might be recursing and that > should be indicated reliably with PF_MEMALLOC. Wanna prep a patch for > it? Sure, I will keep your commit message and authorship (if you are ok with it). > > Thanks. > > -- > tejun
