From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
sakari.ailus@linux.intel.com, mchehab@kernel.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] media: omap3isp change to devm for resources
Date: Fri, 16 Dec 2016 14:19:44 +0200 [thread overview]
Message-ID: <2253735.S1P71dP0gH@avalon> (raw)
In-Reply-To: <56d66910-1776-26a5-53fc-20e44fea490b@xs4all.nl>
Hi Hans,
On Friday 16 Dec 2016 12:39:49 Hans Verkuil wrote:
> On 15/12/16 20:40, Shuah Khan wrote:
> > Using devm resources that have external dependencies such as a dev
> > for a file handler could result in devm resources getting released
> > durin unbind while an application has the file open holding pointer
> > to the devm resource. This results in use-after-free errors when the
> > application exits.
>
> That's solving the wrong problem.
>
> The real problem is that when registering a video_device it should do
> this:
>
> devnode->cdev.kobj.parent = &devnode->dev.kobj;
>
> (taken from cec-core.c)
>
> This will prevent isp->dev from being released as long as there is a
> filehandle still open.
But it won't be enough, devm_* resources are released at unbind time, not at
device release time. Right after the unbind (.remove() for platform devices)
handler returns, devm_kzalloc allocated memory goes away.
> After that change I believe that this will work correctly, but this
> has to be tested first!
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-12-16 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 19:40 [PATCH 0/2] omap3 devm usage removal Shuah Khan
2016-12-15 19:40 ` [PATCH 1/2] media: omap3isp fix media_entity_cleanup() after media device unregister Shuah Khan
2016-12-15 22:32 ` Laurent Pinchart
2016-12-15 22:53 ` Shuah Khan
2016-12-15 19:40 ` [PATCH 2/2] media: omap3isp change to devm for resources Shuah Khan
2016-12-15 22:33 ` Laurent Pinchart
2016-12-15 22:51 ` Shuah Khan
2016-12-15 23:06 ` Laurent Pinchart
2016-12-16 8:17 ` kbuild test robot
2016-12-16 11:39 ` Hans Verkuil
2016-12-16 12:19 ` Laurent Pinchart [this message]
2016-12-16 12:34 ` Hans Verkuil
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=2253735.S1P71dP0gH@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shuahkh@osg.samsung.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 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.