On Thu, 31 May 2018, Matthew Wilcox wrote: > > Freeing a page in the page allocator also was traditionally not sleeping. > > That has changed? > > No. "Your bug" being "The bug in your static analysis tool". It probably > isn't following the data flow correctly (or deeply enough). Well ok this is not going to trigger for kfree(), this is x86 specific and requires CONFIG_DEBUG_PAGEALLOC and a free of a page in a huge page. Ok that is a very contorted situation but how would a static checker deal with that?
