Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp470834ybt; Wed, 1 Jul 2020 02:58:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxfAkGcYAIziXoJMgvl5FqeB1kpODyOFzhXk0HWEBPy9BZY7slQvo7kFsy0kqzkdoMiZqvo X-Received: by 2002:a17:906:27c9:: with SMTP id k9mr21631538ejc.74.1593597531824; Wed, 01 Jul 2020 02:58:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593597531; cv=none; d=google.com; s=arc-20160816; b=Y8qaz06VMK0XpeM2T0JuB7+F04Ua0nEmsgkIyK3SmXgkVygCYzmU95mQ/yqI5uP63q JkFnJHECV1N5yqldMo+cVsSeszdnkYCMogO+AL2bJEUy3QjWn9CiMzL7jK+9VTXMo2nT ++awZZCYXA0Ukq6Gm6JCRXwEOXhqwu0Ex8YH/8k8uze3uDpQesL6+v1MZiLCtFSQ5oUP FyKqZg5ulsimk2mC5tgVxNWltKgnD9uP46Jni3vsR6USmJclAyTseBPYE7LRZ5Lfct4N NpAdiWlnUtybJ8ZVC6ps/mcI0NzOEAP0aA1AcBpyaqGGeM8AWlaKzXw06QQfBJn7OcGc Bjjw== 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:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=/XvXQjiF6V15QWxLpJZj6SwNS1hi9MvwX6STKN2pvlg=; b=hYfIFPL7Q3px3hGWlqvTB4AnjcWRKRkoMipk5/IjwS30rzreBfECs+/qlh9KpEqAcP heiwmqZQDltl6ploiFxhxjGImt02JmnSUXvqLqzsdfgenQEJXFEOjNKf37YrRF/MZlj6 rmRtkAzV3tXZombX2m+X1knouLl5w/8s0kfxv6zxXBUuXs2tciMBPRAQTdxNtITP8Vlx zJW0K07QTaVjG/1YPu7S/zsTHgwR1pja9P/UFG4cl5ptPvlHm2aDArVrlRiFULT7TNE6 4/FWAkCjaAC3rZmN0mw4B43Kgo8IVxP3LbyMeKW18UvqKS0U8gBsiXYM6/DwFzQm5QYm udCQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dn16si4233206ejc.427.2020.07.01.02.58.28; Wed, 01 Jul 2020 02:58:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729770AbgGAJ6R (ORCPT + 99 others); Wed, 1 Jul 2020 05:58:17 -0400 Received: from mail.loongson.cn ([114.242.206.163]:38934 "EHLO loongson.cn" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729332AbgGAJ6Q (ORCPT ); Wed, 1 Jul 2020 05:58:16 -0400 Received: from [10.130.0.52] (unknown [113.200.148.30]) by mail.loongson.cn (Coremail) with SMTP id AQAAf9Dx_98uXvxecKNNAA--.1551S3; Wed, 01 Jul 2020 17:58:08 +0800 (CST) Subject: Re: [PATCH v4 14/14] irqchip/xilinx-intc: Fix potential resource leak To: Markus Elfring , Thomas Gleixner , Jason Cooper , Marc Zyngier , Michal Simek , linux-arm-kernel@lists.infradead.org References: <1593569786-11500-1-git-send-email-yangtiezhu@loongson.cn> <1593569786-11500-15-git-send-email-yangtiezhu@loongson.cn> Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org From: Tiezhu Yang Message-ID: <9434711b-96c1-8ef5-79b6-510170654df8@loongson.cn> Date: Wed, 1 Jul 2020 17:58:06 +0800 User-Agent: Mozilla/5.0 (X11; Linux mips64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CM-TRANSID: AQAAf9Dx_98uXvxecKNNAA--.1551S3 X-Coremail-Antispam: 1UD129KBjvdXoWrKFyxWw4DGFyUKw47tw15CFg_yoW3ZFg_Zr 1093Z5GFW8Jrn8JayIyrsI9393Wr4kJan7tFWvva47Z34fXws3urWqkw1xX348WF1fCF45 Cw4YvrWftrW7ZjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbcAYjsxI4VWDJwAYFVCjjxCrM7AC8VAFwI0_Gr0_Xr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8CjxkF64kEwVA0rcxSw2x7M28EF7xvwVC0I7IYx2IY67AKxVW8JVW5JwA2z4x0Y4vE2Ix0 cI8IcVCY1x0267AKxVWxJVW8Jr1l84ACjcxK6I8E87Iv67AKxVWxJr0_GcWl84ACjcxK6I 8E87Iv6xkF7I0E14v26rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI 64kE6c02F40Ex7xfMcIj6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVW8JVWxJw Am72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IY64vIr41lc7I2V7IY0VAS07AlzVAYIcxG8wCF 04k20xvY0x0EwIxGrwCFx2IqxVCFs4IE7xkEbVWUJVW8JwC20s026c02F40E14v26r1j6r 18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_Jw0_GFylIxkGc2Ij64vI r41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr 1lIxAIcVCF04k26cxKx2IYs7xG6rWUJVWrZr1UMIIF0xvEx4A2jsIE14v26r4j6F4UMIIF 0xvEx4A2jsIEc7CjxVAFwI0_Gr1j6F4UJbIYCTnIWIevJa73UjIFyTuYvjxUc9mRUUUUU X-CM-SenderInfo: p1dqw3xlh2x3gn0dqz5rrqw2lrqou0/ Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/01/2020 05:42 PM, Markus Elfring wrote: >> In the function xilinx_intc_of_init(), system resource "irqc->root_domain" >> was not released in the error case. Thus add jump target for the completion >> of the desired exception handling. > Another small wording adjustment: > … Thus add a jump target … OK > > > … >> +++ b/drivers/irqchip/irq-xilinx-intc.c > … >> @@ -250,6 +250,8 @@ static int __init xilinx_intc_of_init(struct device_node *intc, >> >> return 0; >> >> +error_domain_remove: >> + irq_domain_remove(irqc->root_domain); >> error: >> iounmap(irqc->base); > … > > Can labels like “remove_irq_domain” and “unmap_io” be nicer? Thank you, I will use "err_domain_remove" and "err_iounmap" to keep consistence with other patches. > > Regards, > Markus