* [RFC PATCH v2 07/12] fs/btrfs/extent_io: update usage of address zone modifiers
@ 2018-05-21 18:01 Huaisheng HS1 Ye
0 siblings, 0 replies; only message in thread
From: Huaisheng HS1 Ye @ 2018-05-21 18:01 UTC (permalink / raw)
To: akpm, linux-mm, willy
Cc: mhocko, vbabka, mgorman, kstewart, alexander.levin, gregkh,
colyli, NingTing Cheng, Ocean HY1 He, linux-kernel, iommu,
xen-devel, linux-btrfs, hch, clm, jbacik, dsterba
Use __GFP_ZONE_MASK to replace (__GFP_DMA32 | __GFP_HIGHMEM).
In function alloc_extent_state, it is obvious that __GFP_DMA is not
the expecting zone type.
___GFP_DMA, ___GFP_HIGHMEM and ___GFP_DMA32 have been deleted from GFP
bitmasks, the bottom three bits of GFP mask is reserved for storing
encoded zone number.
__GFP_DMA, __GFP_HIGHMEM and __GFP_DMA32 should not be operated with
each others by OR.
Signed-off-by: Huaisheng Ye <yehs1@lenovo.com>
Cc: Chris Mason <clm@fb.com>
Cc: Josef Bacik <jbacik@fb.com>
Cc: David Sterba <dsterba@suse.com>
---
fs/btrfs/extent_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
index dfeb74a..6653e9a 100644
--- a/fs/btrfs/extent_io.c
+++ b/fs/btrfs/extent_io.c
@@ -220,7 +220,7 @@ static struct extent_state *alloc_extent_state(gfp_t mask)
* The given mask might be not appropriate for the slab allocator,
* drop the unsupported bits
*/
- mask &= ~(__GFP_DMA32|__GFP_HIGHMEM);
+ mask &= ~__GFP_ZONE_MASK;
state = kmem_cache_alloc(extent_state_cache, mask);
if (!state)
return state;
--
1.8.3.1
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-05-21 18:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-21 18:01 [RFC PATCH v2 07/12] fs/btrfs/extent_io: update usage of address zone modifiers Huaisheng HS1 Ye
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox