Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3949237ybg; Mon, 28 Oct 2019 23:15:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqzYrlcOjreQwFO1fQXiiBXtcSW9S74Z4bmySoikmvHTAgVNJI5PTm5sLfT2UHghcih5cbSB X-Received: by 2002:a17:906:e243:: with SMTP id gq3mr1572941ejb.302.1572329705232; Mon, 28 Oct 2019 23:15:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572329705; cv=none; d=google.com; s=arc-20160816; b=SXb340RIJ+/vGwgNbCP/SFGyWVXi4jfrt6VzM/ABDvGQc9Cb5ZI7S7Rn8WTViwWB/K J8EvnddMBc/u55w0sav41hh5roE9GgYWpNFH+12BRC13Kgx8LfMY4xXcJpTxuOFtIXgB egBxTR6cpsNNAGOOGk9Rzl1zB4j4QkMEsJEF0ktLFSgEYUDJSJpmRKQSrrqITfUY25I6 2FSj2DKglBWcNHlz8tIDultoDVz/gsK1rwlY2s7OsFNnC3xeLNH5s+AZF8qnSzEZuC3N jmK8+a8Tvks4zovKxitNsCjesUgrG0NN742hyuBSYQnexwd4V8TmwUEyyLsyfmTWb2BX OEMg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=2PvQalHUmw+CkAdD4s097AVsDtUomtsfmlc1ix/qg7g=; b=r1dLajgxQcWScfne0DSLT723OsPDMCGRMyfBUfGV3c0NcONrq3ctMp2yMw2xXGL449 9ZhCNOITmtJtNMdRazQ55oSWhMSIPSuc3uvJBnfjb/oD/FPG5FLYkydffZL2qvuVEvqL T2aMDhDbYie7151l5A6+Fu9QuaKJ/1t+afr6dZzzw3G7vpC4mIbr08aoyTRSkM0c9iAN AjLLys70CIortAyqmKV38WWhaEVX/NInaOFYxin0fkkZutdfUHsa0hm3U3j5hDfrcKin uEYQp1sddqZ5imLeXEJV5FMDIPXcfsVvz91x5YOBFXlzTsGh7oz8HKXkVsIt5P1F0xka fCUw== ARC-Authentication-Results: i=1; mx.google.com; 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 s6si9792006edi.154.2019.10.28.23.14.41; Mon, 28 Oct 2019 23:15:05 -0700 (PDT) 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; 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 S2403873AbfJ1QsD (ORCPT + 99 others); Mon, 28 Oct 2019 12:48:03 -0400 Received: from webclient5.webclient5.de ([136.243.32.184]:55093 "EHLO webclient5.webclient5.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2403866AbfJ1QsC (ORCPT ); Mon, 28 Oct 2019 12:48:02 -0400 X-Greylist: delayed 447 seconds by postgrey-1.27 at vger.kernel.org; Mon, 28 Oct 2019 12:48:01 EDT Received: from olorin.ladisch.de (x2f7f95e.dyn.telefonica.de [2.247.249.94]) by webclient5.webclient5.de (Postfix) with ESMTPSA id 7F6BC5583F65; Mon, 28 Oct 2019 17:40:32 +0100 (CET) Subject: Re: [PATCH] ALSA: usb-audio: Fix memory leak in __snd_usbmidi_create To: Navid Emamdoost Cc: Takashi Iwai , Navid Emamdoost , Kangjie Lu , Stephen McCamant , Jaroslav Kysela , alsa-devel@alsa-project.org, LKML References: <20191027221007.14317-1-navid.emamdoost@gmail.com> From: Clemens Ladisch Message-ID: Date: Mon, 28 Oct 2019 17:38:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.99.4 at webclient5 X-Virus-Status: Clean Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Navid Emamdoost wrote: > On Mon, Oct 28, 2019 at 1:27 AM Takashi Iwai wrote: >> On Sun, 27 Oct 2019 23:10:06 +0100, >> Navid Emamdoost wrote: >>> In the implementation of __snd_usbmidi_create() there is a memory leak >>> caused by incorrect goto destination. Go to free_midi if >>> snd_usbmidi_create_endpoints_midiman() or snd_usbmidi_create_endpoints() >>> fail. >> >> No, this will lead to double-free. After registering the rawmidi >> interface at snd_usbmidi_create_rawmidi(), the common destructor will >> be called via rawmidi private_free callback, and this will release the >> all resources already. > > Now I can see how rawmidi private_free is set up to release the > resources, but what concerns me is that at the moment of endpoint/port > creation umidi is not yet added to the midi_list. > In other words, what I see is that we still have just one local > pointer to umidi if any of snd_usbmidi_create_endpoint* fail. The snd_rawmidi device is automatically registered with the card, so the line "rmidi->private_free = snd_usbmidi_rawmidi_free;" is the exact point where the ownership of umidi changes. midi_list does not matter. Regards, Clemens