From mboxrd@z Thu Jan 1 00:00:00 1970 From: Namhyung Kim Subject: [PATCH] epoll: use kmalloc() in ep_alloc() Date: Wed, 12 Jan 2011 21:19:55 +0900 Message-ID: <1294834795-3987-1-git-send-email-namhyung@gmail.com> Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Alexander Viro , Davide Libenzi Return-path: Received: from mail-px0-f174.google.com ([209.85.212.174]:40507 "EHLO mail-px0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751368Ab1ALMUG (ORCPT ); Wed, 12 Jan 2011 07:20:06 -0500 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Use kmalloc() instead of kzalloc() in ep_alloc(). It seems that no need to zero-initialize struct eventpoll simply because all of the fields in the struct will be set properly right after. The struct might contain paddings in it but IMHO it would not be a problem since it will not be accessed from the outside of epoll code. Signed-off-by: Namhyung Kim --- fs/eventpoll.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fs/eventpoll.c b/fs/eventpoll.c index 2e21fb85b8b6..bdea67ed9762 100644 --- a/fs/eventpoll.c +++ b/fs/eventpoll.c @@ -728,7 +728,7 @@ static int ep_alloc(struct eventpoll **pep) user = get_current_user(); error = -ENOMEM; - ep = kzalloc(sizeof(*ep), GFP_KERNEL); + ep = kmalloc(sizeof(*ep), GFP_KERNEL); if (unlikely(!ep)) goto free_uid; -- 1.7.3.4.600.g982838b0