Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4166927imu; Tue, 18 Dec 2018 10:05:20 -0800 (PST) X-Google-Smtp-Source: AFSGD/VBS78ZwzU8DBTo9+B+81+j0wsGJYKklDRiKqOTTW7sWDuo+RAgGuylaNieRugX3F+DeUE2 X-Received: by 2002:a63:f109:: with SMTP id f9mr16436535pgi.286.1545156320825; Tue, 18 Dec 2018 10:05:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545156320; cv=none; d=google.com; s=arc-20160816; b=A8jPQOtmzEXZFWaKcuwza/KLJEtCNtceWxiKetbkGpyzthNJIJcvVWQ6slgqqQ4mN/ EtEOHlZOnT8HXDk9NqZC39tssM7fdAfbxmnvwY2Edlhewn2E34h8LuRXcoOusQQA18W3 cjh267VOCbFrbKEgAKJIrMAqixExDhEWDMz9Uu0HaUQr1B7woryHBDv+X+6MEp0lAD22 3dmb5ScmEzxQ0y415bMXXW/UQI4ARrsb4i1EYLjmxrWLWZyWByoK8kNi06SXRpScLeUw ThsHb7nLOLXGK/9n6o5Qbevr51jw30dppOa35ejWxA2vujE8DgEmX/VxTMD00cg5jNR6 b2wQ== 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=PfJ3W9WBEPPAcG320BZyn+cfjk/uPAFqfxmrp5WXxT4=; b=EzRHKEXVL/fwNqvt0vAJHMmVFXfMxxUwsueUkLu8spmVPabBcxDxdlvv+DzWt+ffKl 5JiSRMRxw5GaYyXR+UPySif000m4laiNVq62LOCAOVbK2JsC+bL7ZAO3flUWmPG+4I7l r9Eq8IvpxI5Tlc5CdAZiOk0Drpd8t/jPu6ReysnulkW9BsRhO0q0uwOo0wxV67k19UkU mit6wspzpv3cTOE5r8eZ6NuSCbvKKRdANKnBNB2Xg9PG9vlZGZY6JlMchc91KTjlok+l mmxl8JfW3sZG15zdKyA+HDQ7WQnNNBrxxYrazOkBUjnPv95ho/cRo53mJgEYE+ClKDk/ /a/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=oGSi182J; 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 g20si14116834pgh.241.2018.12.18.10.05.04; Tue, 18 Dec 2018 10:05:20 -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=oGSi182J; 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 S1727586AbeLRQlo (ORCPT + 99 others); Tue, 18 Dec 2018 11:41:44 -0500 Received: from mail.kernel.org ([198.145.29.99]:39254 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726822AbeLRQlk (ORCPT ); Tue, 18 Dec 2018 11:41:40 -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 D61F421873; Tue, 18 Dec 2018 16:41:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1545151300; bh=5WC7GSKRjy0uI/1uUerwSs1j+1qP5CaOJVcrwTnYro8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=oGSi182JahpsNTSMKHeIbrsCwTm1Z1KcW/cMBYg0iVv25mW63P3E3xTk6rCgv9ESi 9wnk2HNEzS1459JYxR8xft3+h/ZJRp2L0oDFI7Xkh3QAfwDQkaD53G4/rjdIKrMKk3 ndrMkeFwhHxYNy3DMuhkc9bwsAGYNXiylc4m7VM4= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Tom Zanussi , "Steven Rostedt (VMware)" Subject: [PATCH 4.19 28/44] tracing: Fix memory leak in set_trigger_filter() Date: Tue, 18 Dec 2018 17:39:40 +0100 Message-Id: <20181218163930.774006911@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20181218163927.119623235@linuxfoundation.org> References: <20181218163927.119623235@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 4.19-stable review patch. If anyone has any objections, please let me know. ------------------ From: Steven Rostedt (VMware) commit 3cec638b3d793b7cacdec5b8072364b41caeb0e1 upstream. When create_event_filter() fails in set_trigger_filter(), the filter may still be allocated and needs to be freed. The caller expects the data->filter to be updated with the new filter, even if the new filter failed (we could add an error message by setting set_str parameter of create_event_filter(), but that's another update). But because the error would just exit, filter was left hanging and nothing could free it. Found by kmemleak detector. Cc: stable@vger.kernel.org Fixes: bac5fb97a173a ("tracing: Add and use generic set_trigger_filter() implementation") Reviewed-by: Tom Zanussi Signed-off-by: Steven Rostedt (VMware) Signed-off-by: Greg Kroah-Hartman --- kernel/trace/trace_events_trigger.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) --- a/kernel/trace/trace_events_trigger.c +++ b/kernel/trace/trace_events_trigger.c @@ -732,8 +732,10 @@ int set_trigger_filter(char *filter_str, /* The filter is for the 'trigger' event, not the triggered event */ ret = create_event_filter(file->event_call, filter_str, false, &filter); - if (ret) - goto out; + /* + * If create_event_filter() fails, filter still needs to be freed. + * Which the calling code will do with data->filter. + */ assign: tmp = rcu_access_pointer(data->filter);