From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751443AbeAYPVA (ORCPT ); Thu, 25 Jan 2018 10:21:00 -0500 Received: from verein.lst.de ([213.95.11.211]:38898 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750980AbeAYPU7 (ORCPT ); Thu, 25 Jan 2018 10:20:59 -0500 Date: Thu, 25 Jan 2018 16:20:58 +0100 From: Christoph Hellwig To: Johannes Thumshirn Cc: Christoph Hellwig , Sagi Grimberg , Keith Busch , Linux Kernel Mailinglist , Linux NVMe Mailinglist , Dan Carpenter , Roland Dreier Subject: Re: [PATCH] nvme: don't free uuid pointer before printing it Message-ID: <20180125152058.GB1778@lst.de> References: <20180125080925.6019-1-jthumshirn@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180125080925.6019-1-jthumshirn@suse.de> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 25, 2018 at 09:09:25AM +0100, Johannes Thumshirn wrote: > Commit df351ef73789 ("nvme-fabrics: fix memory leak when parsing host ID > option") fixed the leak of 'p' but in case uuid_parse() fails the memory > is freed before the error print that is using it. > > Free it after printing eventual errors. Thanks, applied to nvme-4.16.