f2fs: use GFP_F2FS_ZERO for cleanup
authorChao Yu <yuchao0@huawei.com>
Thu, 25 Jan 2018 10:57:25 +0000 (18:57 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Sat, 27 Jan 2018 21:30:40 +0000 (13:30 -0800)
Clean up codes with GFP_F2FS_ZERO, no logic changes.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/node.c

index 9822c9a3482320c0c8387c80bf2c47e8bdc3cabd..7cded843cf1833c82de053b8e9ef240d8a39c3ab 100644 (file)
@@ -143,11 +143,9 @@ static struct nat_entry *__alloc_nat_entry(nid_t nid, bool no_fail)
        struct nat_entry *new;
 
        if (no_fail)
-               new = f2fs_kmem_cache_alloc(nat_entry_slab,
-                                               GFP_NOFS | __GFP_ZERO);
+               new = f2fs_kmem_cache_alloc(nat_entry_slab, GFP_F2FS_ZERO);
        else
-               new = kmem_cache_alloc(nat_entry_slab,
-                                               GFP_NOFS | __GFP_ZERO);
+               new = kmem_cache_alloc(nat_entry_slab, GFP_F2FS_ZERO);
        if (new) {
                nat_set_nid(new, nid);
                nat_reset_flag(new);