On Wed, Sep 03, 2014 at 07:30:58PM -0700, Andrew Morton wrote: > > PF_MEMALLOC_NOIO is only set for some special processes. I think it > > won't affect much. > > Maybe not now. But once we add hacks like this, people say "goody" and > go and use them rather than exerting the effort to sort out their > deadlocks properly :( There will be more PF_MEMALLOC_NOIO users in > 2019. We got PF_MEMALLOC_NOIO because we failed to get vmalloc deadlocks fixed. The reason vmalloc didn't get fixed? "there will be more vmalloc users". > Dunno, I'd like to hear David's thoughts but perhaps it would be better > to find some way to continue to permit PF_MEMALLOC_NOIO to shrink VFS > caches for most filesystems and find some fs-specific fix for ocfs2. > That would mean testing PF_MEMALLOC_NOIO directly I guess. No special flags in the superblock shrinker, please. We have tens of other filesystem shrinkers that might be impacted, too. If we do not want filesystem shrinkers (note the plural) to run, the shrink_control->gfp_mask needs to have __GFP_FS cleared from it when it is first configured and so that context is constant across all shrinker reclaim cases. If you're really worried by changing PF_MEMALLOC_NOIO, then we can introduce PF_MEMALLOC_NOFS and have the mm subsystem mask both flags appropriately when setting the gfp_mask in the shrink_control settings. But fundamentally, our reclaim heirarchy defines that NOIO implies NOFS, and so we need to fix PF_MEMALLOC_NOIO anyway. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
