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 6892CC4332F for ; Tue, 14 Nov 2023 12:28:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232838AbjKNM2E (ORCPT ); Tue, 14 Nov 2023 07:28:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45524 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229798AbjKNM2C (ORCPT ); Tue, 14 Nov 2023 07:28:02 -0500 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C8E8F13A for ; Tue, 14 Nov 2023 04:27:59 -0800 (PST) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2D5C4C433C7; Tue, 14 Nov 2023 12:27:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1699964879; bh=OOtLX4L5bvbZ/lYycLXinIfawDRqNeWMFk6Eb+zcll0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tnn+9IFg9FBefbaw+BFnxwDnMO7Br7OzuHOvhjxsuAg139WQPvbtl0KHsFDCdFav6 lufPJUJSW+J9s2Svbvr627euOvntzMRVuHJJXAXutAxDB1FAJuZB/v28HfsBZcqW3Y UhE2slJwbYmfu5UOEWW5RnGuQVH11UCVGvrt5tw4= Date: Tue, 14 Nov 2023 07:27:57 -0500 From: Greg Kroah-Hartman To: Bartosz Golaszewski Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, Bartosz Golaszewski , Marc Zyngier , Linus Walleij , Wolfram Sang Subject: Re: [PATCH 2/2] genirq: proc: fix a procfs entry leak Message-ID: <2023111440-stray-uncloak-484c@gregkh> References: <873502971b.ffs@tglx> <87msya6wmf.ffs@tglx> <877cpd7a96.ffs@tglx> <87y1hb1ckk.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 13, 2023 at 09:53:47PM +0100, Bartosz Golaszewski wrote: > On Fri, Sep 15, 2023 at 9:50 PM Bartosz Golaszewski wrote: > > > > [snip] > > > > > My point is: the same rule should apply to in-kernel consumers. When > > they request a resource, they get a reference to it. The resource is > > managed by its provider. If the provider is going down, it frees the > > resource. The consumer tries to use it -> it gets an error. I'm not > > convinced by the life-time rules argument. The consumer is not > > CREATING a resource. It's REQUESTING it for usage. IMO this means it > > REFERENCES it, not OWNS it. And so is only responsible for putting the > > reference. > > > > Bartosz > > > > Hi Thomas, Greg et al, > > I am at LPC and will present a talk on Wednesday 5:15pm at the kernel > summit about object life-time issues. I'll reference this problem > among others. Please consider it in your schedules, I think it'll be > useful to discuss it in person as it's a generic problem in many > driver subsystems. Sounds great, I'll try to make it there! greg k-h