From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03C79C3DA6F for ; Fri, 25 Aug 2023 14:59:37 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245136AbjHYO7E (ORCPT ); Fri, 25 Aug 2023 10:59:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35514 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343856AbjHYO6b (ORCPT ); Fri, 25 Aug 2023 10:58:31 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 77A372126 for ; Fri, 25 Aug 2023 07:58:29 -0700 (PDT) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1692975507; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=z50Zlf0WBiUUPkv8o6nl7O/SvnFHeiBLX4CM9sRY9c0=; b=JSIyzlsnNPkjGa2p1xkZtvE7bAfUb+qfBRuuQB8WO2QUGbwne6AYw7X0EaXuKyyykJEWoL hcpt8fgXzq1BrFTKDSOkClB2+2tFUHBeNcetgUcOQUHbp9Hy2zCKUmdXFyz1jH0ZxWzffG oxSIywnt9jcCiLxramh4RH26S/MBsNBJmoiwyiXhgaMUrg8lXLA1UmYHOh5nUAtVASy4Zn v4IRBmzm8y83/8B8sUxJGZ4rORW3FlRJk3dZ/rJ8FpIsWVYvOAIPUu6cfXKngippibTgeu 5fGCv8axgfUnx9vV56YIeukTMuzhaRVXXyIGiyWs2Uk9P0QxbMADCvpbyFWNYw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1692975507; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=z50Zlf0WBiUUPkv8o6nl7O/SvnFHeiBLX4CM9sRY9c0=; b=8gVlLCC4rrTzUBlawMg/1Rgj0PyGxN3V5U8nFSQzsMjfC0DHVkNW1/D5ETPKyzSMwyg5S7 WWWWBjF/V7iyGwAA== To: Bartosz Golaszewski Cc: linux-kernel@vger.kernel.org, Bartosz Golaszewski , Marc Zyngier , Linus Walleij Subject: Re: [PATCH 2/2] genirq: proc: fix a procfs entry leak In-Reply-To: References: <20230814093621.23209-1-brgl@bgdev.pl> <20230814093621.23209-3-brgl@bgdev.pl> <875y54ci86.ffs@tglx> <873507cziz.ffs@tglx> Date: Fri, 25 Aug 2023 16:58:26 +0200 Message-ID: <87v8d3b23x.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 25 2023 at 13:01, Bartosz Golaszewski wrote: > On Fri, Aug 25, 2023 at 10:11=E2=80=AFAM Thomas Gleixner wrote: > I was under the impression that the whole irqnum-to-irq_desc mapping > was designed to handle this situation on purpose, hence a check for > !desc and a silent return in free_irq(). If a missing mapping was a > bug, then it would warrant at least a warning, right? The check for !desc has nothing to do with the problem you are trying to solve. There is obviously a valid interrupt descriptor so desc !=3D NULL, otherwise there would be no procfs entries and no actions, no? Thanks, tglx