Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3330132imu; Sun, 11 Nov 2018 12:31:08 -0800 (PST) X-Google-Smtp-Source: AJdET5d7uTE85nQvhDmMSFrQM61KCEj+t4wkWQibHGdYD5p/Flotz0po4pGwAjJrUU8bBIC4EsDI X-Received: by 2002:aa7:83c2:: with SMTP id j2-v6mr17450131pfn.91.1541968268509; Sun, 11 Nov 2018 12:31:08 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541968268; cv=none; d=google.com; s=arc-20160816; b=aVKCbWvEwBZbjIfrIyDRtmUnTjl2d17JCI7eatzpDFu7j8gdG3iKLQlV392xziIhDv 8q/S5cK8LL8cny9O1Ve+WQuzfTALm9NbnNzxvlfvzYZunqiOsUJcdnfJd8tN2p2WSlt7 35MZeiC7Dbjea0/iHwBgcs922SccmrUVhNmerz4vrBUa59GOYpm6sIA7sZBEWeh8495L 5tV5UA1Bs8tjjQduCexl76LjrQzJ5fDl6MvfXxuR7Q3Dlx8mzzNjFI0UyvrOWn/lAmjz h5l/vTiib8KJfALaGHUNaR5vA2Aw1kkR7fAG7r1rbC1EZfO6bw00PJgRdf9wCOYRPKch d/Ng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:subject:message-id:date:cc:to :from:mime-version:content-transfer-encoding:content-disposition; bh=yTLXSkR2IvfJAkQQznyAcchrXW6jIXO8//OyzKQgKLY=; b=RKIQzsz+5m2H9H96/VUBiTLctzJ/7ZMcS51v8XyQt2qOkdrk1aER2619zJp0z3H6ib /9dmKrZi/iHcV5YJCq1AjC3vGQDbUKuupSr2DyM0Jy/iNLkpF3f+sf01LTS2arRx/TkF hcIXMbE23iX4kzGMtggc7vdxQHucZg4p2qAEJZsdZpWsIeSFlUCruRTeAOzrvVRYd+Cn i6vuarxpVZZ/VcteKmaibK2w/qaOm9cvFL8GRhcuOmgOnWllG9xypHZhrKEnt/hdhuMl YltXRGo1YSy5tsqNY/V/cDNVO8ioDvRBJYZ3kEXZsaoYmvdUyPJ7tXAR6S3xmGHceQTE KJbA== 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 o1-v6si14762606plk.304.2018.11.11.12.30.52; Sun, 11 Nov 2018 12:31: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; 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 S1730626AbeKLGSk (ORCPT + 99 others); Mon, 12 Nov 2018 01:18:40 -0500 Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:50570 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730486AbeKLFsX (ORCPT ); Mon, 12 Nov 2018 00:48:23 -0500 Received: from [192.168.4.242] (helo=deadeye) by shadbolt.decadent.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gLvsh-0000oN-ID; Sun, 11 Nov 2018 19:58:51 +0000 Received: from ben by deadeye with local (Exim 4.91) (envelope-from ) id 1gLvsa-0001rS-8d; Sun, 11 Nov 2018 19:58:44 +0000 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit MIME-Version: 1.0 From: Ben Hutchings To: linux-kernel@vger.kernel.org, stable@vger.kernel.org CC: akpm@linux-foundation.org, "Jonathan Cameron" , "Alison Schofield" , "Ben Hutchings" Date: Sun, 11 Nov 2018 19:49:05 +0000 Message-ID: X-Mailer: LinuxStableQueue (scripts by bwh) Subject: [PATCH 3.16 340/366] iio: iio-trig-periodic-rtc: Free trigger resource correctly In-Reply-To: X-SA-Exim-Connect-IP: 192.168.4.242 X-SA-Exim-Mail-From: ben@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 3.16.61-rc1 review patch. If anyone has any objections, please let me know. ------------------ From: Ben Hutchings This is based on upstream commit 10e840dfb0b7, which did not touch the iio-trig-periodic-rtc driver because it has been removed upstream. The following explanation comes from that commit: These stand-alone trigger drivers were using iio_trigger_put() where they should have been using iio_trigger_free(). The iio_trigger_put() adds a module_put which is bad since they never did a module_get. In the sysfs driver, module_get/put's are used as triggers are added & removed. This extra module_put() occurs on an error path in the probe routine (probably rare). In the bfin-timer & interrupt trigger drivers, the module resources are not explicitly managed, so it's doing a put on something that was never get'd. It occurs on the probe error path and on the remove path (not so rare). Tested with the sysfs trigger driver. The bfin & interrupt drivers were build tested & inspected only. This was build tested only. Cc: Alison Schofield Cc: Jonathan Cameron Signed-off-by: Ben Hutchings Signed-off-by: Ben Hutchings --- drivers/staging/iio/trigger/iio-trig-periodic-rtc.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- a/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c +++ b/drivers/staging/iio/trigger/iio-trig-periodic-rtc.c @@ -123,7 +123,7 @@ static int iio_trig_periodic_rtc_probe(s trig_info = kzalloc(sizeof(*trig_info), GFP_KERNEL); if (!trig_info) { ret = -ENOMEM; - goto error_put_trigger_and_remove_from_list; + goto error_free_trigger_and_remove_from_list; } iio_trigger_set_drvdata(trig, trig_info); trig->ops = &iio_prtc_trigger_ops; @@ -151,9 +151,9 @@ error_close_rtc: rtc_class_close(trig_info->rtc); error_free_trig_info: kfree(trig_info); -error_put_trigger_and_remove_from_list: +error_free_trigger_and_remove_from_list: list_del(&trig->alloc_list); - iio_trigger_put(trig); + iio_trigger_free(trig); error_free_completed_registrations: list_for_each_entry_safe(trig, trig2,