We can cheaply get rid of a few GFP_NOFS, as there are only two contexts, initializaton (GFP_KERNEL is ok), and potentially a "NOFS", but with memalloc_nofs it's made safe.
David Sterba (3): btrfs: add memalloc_nofs protections around alloc_workspace callback btrfs: switch kmallocs to GFP_KERNEL in lzo/zlib alloc_workspace btrfs: switch to kvmalloc and GFP_KERNEL in lzo/zlib alloc_workspace fs/btrfs/compression.c | 10 ++++++++++ fs/btrfs/lzo.c | 16 ++++++++-------- fs/btrfs/zlib.c | 10 +++++----- 3 files changed, 23 insertions(+), 13 deletions(-) -- 2.12.0 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
