From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932869AbcE3J5y (ORCPT ); Mon, 30 May 2016 05:57:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34605 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932697AbcE3J5x (ORCPT ); Mon, 30 May 2016 05:57:53 -0400 From: Vitaly Kuznetsov To: devel@linuxdriverproject.org Cc: linux-kernel@vger.kernel.org, "K. Y. Srinivasan" , Haiyang Zhang Subject: [PATCH 0/2] Drivers: hv: fix memory leak while establishing GPADL Date: Mon, 30 May 2016 11:57:47 +0200 Message-Id: <1464602269-15945-1-git-send-email-vkuznets@redhat.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Mon, 30 May 2016 09:57:52 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org kmemleak helped me to identify a memory leak on GPADL establishment. Do some minor refactoring and fix the issue. Vitaly Kuznetsov (2): Drivers: hv: get rid of redundant messagecount in create_gpadl_header() Drivers: hv: don't leak memory in vmbus_establish_gpadl() drivers/hv/channel.c | 44 +++++++++++++++++++++----------------------- 1 file changed, 21 insertions(+), 23 deletions(-) -- 2.5.5