[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20200926100834.GA184671@rlk>
Date: Sat, 26 Sep 2020 18:08:34 +0800
From: Hui Su <sh_def@....com>
To: akpm@...ux-foundation.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] mm,z3fold: use xx_zalloc instead xx_alloc and memset
alloc_slots() allocate memory for slots by kmem_cache_alloc(),
then memset it, we can just use kmem_cache_zalloc() api.
Signed-off-by: Hui Su <sh_def@....com>
---
mm/z3fold.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/z3fold.c b/mm/z3fold.c
index 460b0feced26..18feaa0bc537 100644
--- a/mm/z3fold.c
+++ b/mm/z3fold.c
@@ -212,13 +212,12 @@ static inline struct z3fold_buddy_slots *alloc_slots(struct z3fold_pool *pool,
{
struct z3fold_buddy_slots *slots;
- slots = kmem_cache_alloc(pool->c_handle,
+ slots = kmem_cache_zalloc(pool->c_handle,
(gfp & ~(__GFP_HIGHMEM | __GFP_MOVABLE)));
if (slots) {
/* It will be freed separately in free_handle(). */
kmemleak_not_leak(slots);
- memset(slots->slot, 0, sizeof(slots->slot));
slots->pool = (unsigned long)pool;
rwlock_init(&slots->lock);
}
--
2.25.1
Powered by blists - more mailing lists