From: Dave Jiang <dave.jiang@intel.com>
To: Dan Williams <dan.j.williams@intel.com>, <nvdimm@lists.linux.dev>
Cc: <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 1/4] dax: Fix dax_mapping_release() use after free
Date: Thu, 15 Jun 2023 10:33:50 -0700 [thread overview]
Message-ID: <b05b81bb-ed3d-ed95-71c9-4d2e30aa017f@intel.com> (raw)
In-Reply-To: <168577283412.1672036.16111545266174261446.stgit@dwillia2-xfh.jf.intel.com>
On 6/2/23 23:13, Dan Williams wrote:
> A CONFIG_DEBUG_KOBJECT_RELEASE test of removing a device-dax region
> provider (like modprobe -r dax_hmem) yields:
>
> kobject: 'mapping0' (ffff93eb460e8800): kobject_release, parent 0000000000000000 (delayed 2000)
> [..]
> DEBUG_LOCKS_WARN_ON(1)
> WARNING: CPU: 23 PID: 282 at kernel/locking/lockdep.c:232 __lock_acquire+0x9fc/0x2260
> [..]
> RIP: 0010:__lock_acquire+0x9fc/0x2260
> [..]
> Call Trace:
> <TASK>
> [..]
> lock_acquire+0xd4/0x2c0
> ? ida_free+0x62/0x130
> _raw_spin_lock_irqsave+0x47/0x70
> ? ida_free+0x62/0x130
> ida_free+0x62/0x130
> dax_mapping_release+0x1f/0x30
> device_release+0x36/0x90
> kobject_delayed_cleanup+0x46/0x150
>
> Due to attempting ida_free() on an ida object that has already been
> freed. Devices typically only hold a reference on their parent while
> registered. If a child needs a parent object to complete its release it
> needs to hold a reference that it drops from its release callback.
> Arrange for a dax_mapping to pin its parent dev_dax instance until
> dax_mapping_release().
>
> Fixes: 0b07ce872a9e ("device-dax: introduce 'mapping' devices")
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dax/bus.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> index 227800053309..aee695f86b44 100644
> --- a/drivers/dax/bus.c
> +++ b/drivers/dax/bus.c
> @@ -635,10 +635,12 @@ EXPORT_SYMBOL_GPL(alloc_dax_region);
> static void dax_mapping_release(struct device *dev)
> {
> struct dax_mapping *mapping = to_dax_mapping(dev);
> - struct dev_dax *dev_dax = to_dev_dax(dev->parent);
> + struct device *parent = dev->parent;
> + struct dev_dax *dev_dax = to_dev_dax(parent);
>
> ida_free(&dev_dax->ida, mapping->id);
> kfree(mapping);
> + put_device(parent);
> }
>
> static void unregister_dax_mapping(void *data)
> @@ -778,6 +780,7 @@ static int devm_register_dax_mapping(struct dev_dax *dev_dax, int range_id)
> dev = &mapping->dev;
> device_initialize(dev);
> dev->parent = &dev_dax->dev;
> + get_device(dev->parent);
> dev->type = &dax_mapping_type;
> dev_set_name(dev, "mapping%d", mapping->id);
> rc = device_add(dev);
>
next prev parent reply other threads:[~2023-06-15 17:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 6:13 [PATCH 0/4] dax: Fix use after free and other cleanups Dan Williams
2023-06-03 6:13 ` [PATCH 1/4] dax: Fix dax_mapping_release() use after free Dan Williams
2023-06-04 2:40 ` Ira Weiny
[not found] ` <CGME20230605204543uscas1p19d1b3a00134805c5c3e738dea4ee4728@uscas1p1.samsung.com>
2023-06-05 20:45 ` Fan Ni
2023-06-15 17:33 ` Dave Jiang [this message]
2023-06-03 6:13 ` [PATCH 2/4] dax: Use device_unregister() in unregister_dax_mapping() Dan Williams
2023-06-04 2:41 ` Ira Weiny
[not found] ` <CGME20230605204615uscas1p1931142de4b55be03c99f513b51dcb2fc@uscas1p1.samsung.com>
2023-06-05 20:46 ` Fan Ni
2023-06-15 17:34 ` Dave Jiang
2023-06-03 6:14 ` [PATCH 3/4] dax: Introduce alloc_dev_dax_id() Dan Williams
2023-06-04 2:57 ` Ira Weiny
2023-06-16 1:22 ` Dan Williams
2023-06-16 22:11 ` Ira Weiny
2023-06-03 6:14 ` [PATCH 4/4] dax: Cleanup extra dax_region references Dan Williams
2023-06-04 2:58 ` Ira Weiny
2023-06-06 17:46 ` Fan Ni
2023-06-06 20:42 ` Ira Weiny
2023-06-15 17:45 ` Dave Jiang
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=b05b81bb-ed3d-ed95-71c9-4d2e30aa017f@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).