From: Dave Jiang <dave.jiang@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: vkoul@kernel.org, Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v3] dmaengine: idxd: Do not use devm for 'struct device' object allocation
Date: Sat, 27 Feb 2021 09:27:26 -0700 [thread overview]
Message-ID: <1482a4fc-3359-e807-d8ac-8fa7a2e110ab@intel.com> (raw)
In-Reply-To: <20210227013641.GC4247@nvidia.com>
On 2/26/2021 6:36 PM, Jason Gunthorpe wrote:
> On Wed, Feb 24, 2021 at 03:35:19PM -0700, Dave Jiang wrote:
>> Remove devm_* allocation of memory of 'struct device' objects.
>> The devm_* lifetime is incompatible with device->release() lifetime.
>> Address issues flagged by CONFIG_DEBUG_KOBJECT_RELEASE. Add release
>> functions for each component in order to free the allocated memory at
>> the appropriate time. Each component such as wq, engine, and group now
>> needs to be allocated individually in order to setup the lifetime properly.
> You've tested this now with kasn and all the other debugging turned
> on?
Only with DEBUG_KOBJECT_RELEASE. I wasn't aware of the kasn tests. I'll
go test with those. Thanks for the thorough review. Really appreciate it.
> I poked around a bit and there are other bugs in here too:
>
> static int idxd_wq_cdev_dev_setup(struct idxd_wq *wq)
> {
> idxd_cdev->dev = kzalloc(sizeof(*idxd_cdev->dev), GFP_KERNEL);
> dev_set_name(dev, "%s/wq%u.%u", idxd_get_dev_name(idxd), idxd->id, wq->id);
> ^^^ Missing error check
>
> if (minor < 0) {
> rc = minor;
> kfree(dev);
> ^^^^ leaks the memory dev_set_name allocated
>
> You must call device_initialize before calling dev_set_name and once
> device_initialize is called it must do put_device to clean
> up. put_device will free memory allocated by dev_set_name
>
> Isn't this a use after free kasn should flag?
>
> device_unregister(idxd_cdev->dev);
> ida_simple_remove(&cdev_ctx->minor_ida, idxd_cdev->minor);
> ^^^^^^
> idxd_cdev may
> have been freed by device_unregister
>
> Probably a good idea to check all the places working with struct
> device carefully to see that they are right
>
> Jason
next prev parent reply other threads:[~2021-02-27 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 22:35 [PATCH v3] dmaengine: idxd: Do not use devm for 'struct device' object allocation Dave Jiang
2021-02-27 1:36 ` Jason Gunthorpe
2021-02-27 16:27 ` Dave Jiang [this message]
2021-02-27 23:57 ` Jason Gunthorpe
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=1482a4fc-3359-e807-d8ac-8fa7a2e110ab@intel.com \
--to=dave.jiang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jgg@nvidia.com \
--cc=vkoul@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.