From: Wolfram Sang <wsa@the-dreams.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
iommu@lists.linux-foundation.org,
linux-renesas-soc@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] dma-mapping: introduce helper for setting dma_parms
Date: Wed, 12 Sep 2018 01:39:33 +0200 [thread overview]
Message-ID: <20180911233933.GA1402@kunai> (raw)
In-Reply-To: <a9478a05-5908-e693-7eeb-3673b2facda7@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]
Hi Robin,
> > od = devm_kzalloc(&pdev->dev, sizeof(*od), GFP_KERNEL);
> > if (!od)
> > return -ENOMEM;
> >
> > pdev->dev.dma_parms = &od->dma_parms;
> > dma_set_max_seg_size(&pdev->dev, 0x3FFFFFFF);
> >
> > And that's all about handling dma_parms. So, on unbind, the memory for
> > 'od' gets freed and dma_params is a dangling pointer.
>
> That's the typical case - the dma_parms structure is simply embedded in some
> other private data which tends to have the appropriate lifetime anyway. I
> can't see that the dangling pointer is an issue when it's set
> unconditionally on probe and valid until remove, because anyone
> dereferencing dev->dma_parms when dev has no driver bound is doing something
> very very wrong anyway. I suppose we could zero it in
> __device_release_driver() for good measure though - shame we've found
> something dma_deconfigure() could have been useful for just after we killed
> it ;)
I see. Yes, I was aware that the misuse of this dangling pointer is
somewhat academical. Yet, it was easy to fix and clearing this pointer
is good programming practice, I'd say. I agree that clearing the pointer
in __device_release_driver is a good option, too, if documentation about
its expected life cycle (== get's cleared on unbind) is clear about
that. Probably that life cycle confusion led to the more complicated
code in the exynos_drm driver. I will look into all of that tomorrow.
> Note that ultimately we'd like to have a single structure to hold all the
> masks and other gubbins (per the very original intent of dma_parms), so
I was wondering about that, yes.
> there's a fair chance of this getting fundamentally rejigged at some point
> anyway.
Makes sense. Yet, as this change is gonna be small, I think it's still
nice to have.
Thanks for the input!
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-09-11 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 16:30 [RFC PATCH 0/2] dma-mapping: introduce helper for setting dma_parms Wolfram Sang
2018-09-11 16:30 ` [RFC PATCH 1/2] " Wolfram Sang
2018-09-11 16:30 ` [RFC PATCH 2/2] mmc: sdhi: internal_dmac: set dma_parms Wolfram Sang
2018-09-11 17:24 ` [RFC PATCH 0/2] dma-mapping: introduce helper for setting dma_parms Robin Murphy
2018-09-11 23:39 ` Wolfram Sang [this message]
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=20180911233933.GA1402@kunai \
--to=wsa@the-dreams.de \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=wsa+renesas@sang-engineering.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