xfs: xfs_mru_cache_insert() should use GFP_NOFS
authorByoungyoung Lee <blee@gatech.edu>
Wed, 25 Mar 2015 03:57:53 +0000 (14:57 +1100)
committerDave Chinner <david@fromorbit.com>
Wed, 25 Mar 2015 03:57:53 +0000 (14:57 +1100)
commit20dafeefac97d1a690b113f2a954dc84fdf8f290
tree826d1ee45edb8545a27af8bc1f4f494665b1c534
parent65dd297ac25565701fead5e4ee69b9ca62729f0e
xfs: xfs_mru_cache_insert() should use GFP_NOFS

xfs_mru_cache_insert() can be called from within transaction context
during block allocation like so:

write(2)
  ....
    xfs_get_blocks
      xfs_iomap_write_direct
        start transaction
        xfs_bmapi_write
          xfs_bmapi_allocate
            xfs_bmap_btalloc
              xfs_bmap_btalloc_filestreams
                xfs_filestream_new_ag
                  xfs_filestream_pick_ag
                    xfs_mru_cache_insert
                      radix_tree_preload(GFP_KERNEL)

In this case, GFP_KERNEL is incorrect and can potentially lead to
deadlocks in memory reclaim. It should use GFP_NOFS allocations to
avoid lock recursion problems.

[dchinner: rewrote commit message]

Signed-off-by: Byoungyoung Lee <blee@gatech.edu>
Signed-off-by: Sanidhya Kashyap <sanidhya.gatech@gmail.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_mru_cache.c