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 7DC5AC433FE for ; Wed, 2 Feb 2022 18:28:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234373AbiBBS2P (ORCPT ); Wed, 2 Feb 2022 13:28:15 -0500 Received: from mga12.intel.com ([192.55.52.136]:21063 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233830AbiBBS2N (ORCPT ); Wed, 2 Feb 2022 13:28:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643826493; x=1675362493; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=B+ybzEvcSkWC9hIHFoztcZ1HBSXahf3cZDN+xuaqJpk=; b=OHS0WojZaWLjEXfnUrYeensCmNILSPf7U7r9pIePI91AGSodGPwbdHpE upduew+Z4MPv/mIctJUXMHT+B0nD2c9Rg/sV8Fm1AHGdgOrSgPi1i0QbX eWFpPOLYzAUGt48/6+t8Xg37k8SO7PF9kCckI7eYDy4qXGnnApc18ZR+e 6V6RiGSzImp8A9WRwSP/4XGkBlTK6BlJyg1ei32nYMRFTiuMvtovc8bZG x8IvNvi4/QEMvJ54Ot9rJ/OjX1rlBJBmaiM/Xonsg+p0sE+6zv/moM/MR y5fdsuo9+8PAfdky13S2qGcilKZzBuKXLAK+tvR9FyyQcjFIWAzH8rvaQ Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10246"; a="227961496" X-IronPort-AV: E=Sophos;i="5.88,337,1635231600"; d="scan'208";a="227961496" Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Feb 2022 10:28:13 -0800 X-IronPort-AV: E=Sophos;i="5.88,337,1635231600"; d="scan'208";a="534953966" Received: from svenur-mobl2.amr.corp.intel.com (HELO intel.com) ([10.252.133.34]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Feb 2022 10:28:12 -0800 Date: Wed, 2 Feb 2022 10:28:11 -0800 From: Ben Widawsky To: Dan Williams Cc: linux-cxl@vger.kernel.org, patches@lists.linux.dev, Alison Schofield , Ira Weiny , Jonathan Cameron , Vishal Verma , Bjorn Helgaas , Linux NVDIMM , Linux PCI Subject: Re: [PATCH v3 01/14] cxl/region: Add region creation ABI Message-ID: <20220202182811.ivupsaeogyiwl5so@intel.com> References: <20220128002707.391076-1-ben.widawsky@intel.com> <20220128002707.391076-2-ben.widawsky@intel.com> <20220202182604.oangkxomx3npmobl@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220202182604.oangkxomx3npmobl@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-cxl@vger.kernel.org On 22-02-02 10:26:06, Ben Widawsky wrote: > On 22-01-28 10:59:26, Dan Williams wrote: > > On Fri, Jan 28, 2022 at 10:14 AM Dan Williams wrote: > > [..] > > > Here is that put_device() I was expecting, that kfree() earlier was a > > > double-free it seems. > > > > > > Also, I would have expected a devm action to remove this. Something like: > > > > > > struct cxl_port *port = to_cxl_port(cxld->dev.parent); > > > > > > cxl_device_lock(&port->dev); > > > if (port->dev.driver) > > > devm_cxl_add_region(port->uport, cxld, id); > > I assume you mean devm_cxl_delete_region(), yes? > > > > else > > > rc = -ENXIO; > > > cxl_device_unlock(&port->dev); > > > > > > ...then no matter what you know the region will be unregistered when > > > the root port goes away. > > > > ...actually, the lock and ->dev.driver check here are not needed > > because this attribute is only registered while the cxl_acpi driver is > > bound. So, it is safe to assume this is protected as decoder remove > > synchronizes against active sysfs users. > > I'm somewhat confused when you say devm action to remove this. The current auto > region deletion happens when the ->release() is called. Are you suggesting when > the root decoder is removed I delete the regions at that point? Hmm. I went back and looked and I had changed this functionality at some point... So forget I said that, it isn't how it's working currently. But the question remains, are you suggesting I delete in the root decoder unregistration?