Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp677773imu; Fri, 11 Jan 2019 07:14:08 -0800 (PST) X-Google-Smtp-Source: ALg8bN48l4yHBMwQ4jT3Bvw5XCVWWTpMfmx6dBTv/sySMTXtUE87gvoQsprvk2RaqfzPxdsSkKgu X-Received: by 2002:a62:6e07:: with SMTP id j7mr15354562pfc.135.1547219648351; Fri, 11 Jan 2019 07:14:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1547219648; cv=none; d=google.com; s=arc-20160816; b=iG4CFb4WooN6V6ZiKSj/Dj9DAZW1BAdHLefEA9VzzVGhXUFyNCEQAO2GfomlBHmFzg d/q9eqq9Uz46I/3Si+EyqkxH63XIdwrZIDe5pOJuP2bpZF8hEfjKKLuFAama59CdRpKp D6Uq9Bk2U67OGX6FbedNm0VGjV3mjz1MhFrjaG4Kb4SCA1BVqhwpgbeZkt4BrDIgkQ/b dvDIDjsNpkHgQyh84i+LRJBRBj8F2m1STgrin3W7jhcpW0FbgTdDnipfUEFTVtuxr9KV srAzXPD++oD1mEdmZi1d7LQF2VJDOQd+ObjEkmV6DluYteMVKbkd8YmMXBQw+/DhIH38 AJPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=5tYh/WoyXYcxBkvVV5AtmIvBfBQBA0bRmZSZjAmpNIk=; b=jIqmrpQiXJhAziTCwz7Yr1rz1zFFnlS63mmsJ5+LlFXirjY5qqZ1DWwYgvITSFAYjc hGdiB16jiNxl5sjZQ9hVG/6v9AVvHpbfDQ5FZkF2zrAxxbtCZukpLpa+UWcRAVfAJ2sh AfaKxykfQ3P38iBWedgimAzMMGD4g/PwJXSmD+N3Y/JZjSypcjoJLsYcP1d4MUU/Gp88 2JlRcsEhFo5F3QvfG5WBLbENQ6BaxpmohJ59liJEkdHKceD+UGTGQ0JGWYGxUeianUtO C3GNkLdoNEdliP9R2Vz5eDC8GHrCGxTN4fxiAoJ+rcIlUFVX32dQ9xrjoEZ2a6oknuCv 3Ukw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=DGeYtICQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c2si6482930plb.152.2019.01.11.07.13.52; Fri, 11 Jan 2019 07:14:08 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=DGeYtICQ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387511AbfAKOP5 (ORCPT + 99 others); Fri, 11 Jan 2019 09:15:57 -0500 Received: from mail.kernel.org ([198.145.29.99]:60208 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387481AbfAKOPz (ORCPT ); Fri, 11 Jan 2019 09:15:55 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B8F29214D8; Fri, 11 Jan 2019 14:15:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1547216155; bh=5cJXIKY9yJ31Tb9FeWRH4wmim5dWsYfOnLdvHIc8S/A=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=DGeYtICQeaL37ZnTlpZYM9+2nawLYXrCdRFQHHxp7I5rpixAZQt5Lqr9Vy8PsTJMm 45O0Ey+0+i1WISahJe3KWZfWGF433n0YIUkloO5GuNvMQmKolq6KnCE0sHakwMm6sR KH2Y4GRHzIDOzhHXhDR/5ug2YBndSbiIpBiJKMY8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Vasily Averin , David Teigland , stable@kernel.org Subject: [PATCH 3.18 41/47] dlm: memory leaks on error path in dlm_user_request() Date: Fri, 11 Jan 2019 15:08:26 +0100 Message-Id: <20190111131001.460390179@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190111130956.170952125@linuxfoundation.org> References: <20190111130956.170952125@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.18-stable review patch. If anyone has any objections, please let me know. ------------------ From: Vasily Averin commit d47b41aceeadc6b58abc9c7c6485bef7cfb75636 upstream. According to comment in dlm_user_request() ua should be freed in dlm_free_lkb() after successful attach to lkb. However ua is attached to lkb not in set_lock_args() but later, inside request_lock(). Fixes 597d0cae0f99 ("[DLM] dlm: user locks") Cc: stable@kernel.org # 2.6.19 Signed-off-by: Vasily Averin Signed-off-by: David Teigland Signed-off-by: Greg Kroah-Hartman --- fs/dlm/lock.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) --- a/fs/dlm/lock.c +++ b/fs/dlm/lock.c @@ -5795,20 +5795,20 @@ int dlm_user_request(struct dlm_ls *ls, goto out; } } - - /* After ua is attached to lkb it will be freed by dlm_free_lkb(). - When DLM_IFL_USER is set, the dlm knows that this is a userspace - lock and that lkb_astparam is the dlm_user_args structure. */ - error = set_lock_args(mode, &ua->lksb, flags, namelen, timeout_cs, fake_astfn, ua, fake_bastfn, &args); - lkb->lkb_flags |= DLM_IFL_USER; - if (error) { + kfree(ua->lksb.sb_lvbptr); + ua->lksb.sb_lvbptr = NULL; + kfree(ua); __put_lkb(ls, lkb); goto out; } + /* After ua is attached to lkb it will be freed by dlm_free_lkb(). + When DLM_IFL_USER is set, the dlm knows that this is a userspace + lock and that lkb_astparam is the dlm_user_args structure. */ + lkb->lkb_flags |= DLM_IFL_USER; error = request_lock(ls, lkb, name, namelen, &args); switch (error) {