From: Dan Carpenter <dan.carpenter@oracle.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
Sakari Alius <sakari.ailus@iki.fi>,
wharms@bfs.de, linux-media@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] [media] uvcvideo: freeing an error pointer
Date: Wed, 30 Nov 2016 17:45:22 +0300 [thread overview]
Message-ID: <20161130144522.GJ28558@mwanda> (raw)
In-Reply-To: <3099994.m2oKJeJMud@avalon>
On Wed, Nov 30, 2016 at 03:53:03PM +0200, Laurent Pinchart wrote:
> But then you get the following patch (which, apart from being totally made up,
> probably shows what I've watched yesterday evening).
>
> @@ ... @@
> return -ENOMEM;
> }
>
> + ret = check_time_vortex();
> + if (ret < 0)
> + goto power_off_tardis;
> +
> matt_smith = alloc_regeneration();
> if (math_smith->status != OK) {
> ret = -E_NEEDS_FISH_FINGERS_AND_CUSTARD;
>
I don't get it. Did we power on the tardis on the lines before? That's
all the state that you need to keep in your head is just the most
recently allocated thing.
> >From that code only you can't tell whether the jump label is the right one. If
> a single jump label is used with an unwinding code block that supports non-
> allocated resources, you don't have to ask yourself any question.
>
You absolutely do have to ask that question, you just can't answer it
without jumping back and forth. Doing everything at once is logically
more complicated than doing them one thing at a time, and empirically
just from looking at which code has the most bugs, then single exit
labels are the most buggy.
regards,
dan carpenter
next prev parent reply other threads:[~2016-11-30 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 10:28 [patch] [media] uvcvideo: freeing an error pointer Dan Carpenter
2016-11-25 13:40 ` SF Markus Elfring
2016-11-25 13:57 ` Laurent Pinchart
2016-11-25 14:47 ` walter harms
2016-11-25 16:02 ` Laurent Pinchart
2016-11-25 19:20 ` Dan Carpenter
2016-11-27 16:21 ` Sakari Alius
2016-11-28 13:49 ` Dan Carpenter
2016-11-28 13:54 ` Julia Lawall
2016-11-28 14:49 ` Laurent Pinchart
2016-11-30 12:33 ` Dan Carpenter
2016-11-30 13:53 ` Laurent Pinchart
2016-11-30 14:45 ` Dan Carpenter [this message]
2016-11-29 6:48 ` Julia Lawall
2016-11-25 19:08 ` Dan Carpenter
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=20161130144522.GJ28558@mwanda \
--to=dan.carpenter@oracle.com \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=wharms@bfs.de \
/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).