Linux CXL
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Li Ming <ming.li@zohomail.com>, Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<dave@stgolabs.net>, <jonathan.cameron@huawei.com>,
	<dave.jiang@intel.com>, <alison.schofield@intel.com>,
	<vishal.l.verma@intel.com>, <ira.weiny@intel.com>
Subject: Re: [PATCH v2 5/7] cxl/core: Use guard() to drop goto pattern of cxl_dpa_alloc()
Date: Wed, 19 Feb 2025 17:29:52 -0800	[thread overview]
Message-ID: <67b6859048d26_2d1e29482@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <55f67727-ed24-4ac4-97c1-95b65d110daf@zohomail.com>

Li Ming wrote:
[..]
> After __cxl_dpa_alloc(), a 'devm_add_action_or_reset(&port->dev,
> cxl_dpa_release, cxled)' will be invoked, cxl_dpa_rwsem is possible to
> be held in cxl_dpa_release() in devm_add_action_or_reset() failure
> case.
> 
> So I create __cxl_dpa_alloc() to hold cxl_dpa_rwsem for the operations
> needed cxl_dpa_resem protection, make sure that the cxl_dpa_rwsem is
> released before devm_add_action_or_reset() invoking.

Ah, got it, missing context, makes sense.

  reply	other threads:[~2025-02-20  1:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 14:48 [PATCH v2 0/7] Use guard() instead of rwsem locking Li Ming
2025-02-17 14:48 ` [PATCH v2 1/7] cxl/core: Use guard() to replace open-coded down_read/write() Li Ming
2025-02-19 17:11   ` Dave Jiang
2025-02-19 17:33   ` Alison Schofield
2025-02-17 14:48 ` [PATCH v2 2/7] cxl/core: cxl_mem_sanitize() cleanup Li Ming
2025-02-19 17:12   ` Dave Jiang
2025-02-19 17:34   ` Alison Schofield
2025-02-17 14:48 ` [PATCH v2 3/7] cxl/memdev: cxl_memdev_ioctl() cleanup Li Ming
2025-02-19 17:16   ` Dave Jiang
2025-02-19 17:35   ` Alison Schofield
2025-02-17 14:48 ` [PATCH v2 4/7] cxl/core: Use guard() to drop the goto pattern of cxl_dpa_free() Li Ming
2025-02-19 17:19   ` Dave Jiang
2025-02-19 17:36   ` Alison Schofield
2025-02-17 14:48 ` [PATCH v2 5/7] cxl/core: Use guard() to drop goto pattern of cxl_dpa_alloc() Li Ming
2025-02-19 17:21   ` Dave Jiang
2025-02-19 17:36   ` Alison Schofield
2025-02-20  1:01   ` Dan Williams
2025-02-20  1:26     ` Li Ming
2025-02-20  1:29       ` Dan Williams [this message]
2025-02-17 14:48 ` [PATCH v2 6/7] cxl/region: Drop goto pattern in cxl_dax_region_alloc() Li Ming
2025-02-19 17:23   ` Dave Jiang
2025-02-19 17:37   ` Alison Schofield
2025-02-17 14:48 ` [PATCH v2 7/7] cxl/region: Drop goto pattern of construct_region() Li Ming
2025-02-18 17:24   ` Jonathan Cameron
2025-02-19 17:24   ` Dave Jiang
2025-02-19 17:38   ` Alison Schofield
2025-02-20  1:04   ` Dan Williams
2025-02-20  1:42     ` Li Ming
2025-02-18 17:54 ` [PATCH v2 0/7] Use guard() instead of rwsem locking Davidlohr Bueso
2025-02-19 20:46 ` Ira Weiny
2025-02-19 21:09 ` Dave Jiang
2025-02-20  0:43   ` Li Ming

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67b6859048d26_2d1e29482@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --cc=vishal.l.verma@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox