linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 1/1] media: Set entity->links NULL in cleanup
Date: Wed, 24 Sep 2014 12:17:45 +0300	[thread overview]
Message-ID: <54228C39.7080207@linux.intel.com> (raw)
In-Reply-To: <4899501.NLaQ1XGmm5@avalon>

Hi Laurent,

Oops. this got buried in my inbox...

Laurent Pinchart wrote:
> On Thursday 17 July 2014 14:53:49 Sakari Ailus wrote:
>> On Thu, Jul 17, 2014 at 01:43:09PM +0200, Laurent Pinchart wrote:
>>> On Tuesday 27 May 2014 16:27:49 Sakari Ailus wrote:
>>>> Calling media_entity_cleanup() on a cleaned-up entity would result into
>>>> double free of the entity->links pointer and likely memory corruption as
>>>> well.
>>>
>>> My first question is, why would anyone do that ? :-)
>>
>> Because it makes error handling easier. Many cleanup functions work this
>> way, but not media_entity_cleanup().
>
> Do the cleanup functions support being called multiple times, or do they just
> support being called on memory that has been zeroed and not further
> initialized ? The media_entity_cleanup() function supports the latter.

I'd hope they wouldn't be called multiple times, or on memory that's not 
been zeroed, but in that case it's better to behave rather than corrupt 
system memory. That could be an indication of other problems, too, so 
one could consider adding WARN_ON() to this as well. What do you think?

-- 
Kind regards,

Sakari Ailus
sakari.ailus@linux.intel.com

  reply	other threads:[~2014-09-24  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 13:27 [PATCH 1/1] media: Set entity->links NULL in cleanup Sakari Ailus
2014-07-17 11:43 ` Laurent Pinchart
2014-07-17 11:53   ` Sakari Ailus
2014-07-17 12:13     ` Laurent Pinchart
2014-09-24  9:17       ` Sakari Ailus [this message]
2014-09-26 14:20         ` Laurent Pinchart

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=54228C39.7080207@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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).