From: Moritz Fischer <moritz.fischer@ettus.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
Moritz Fischer <moritz.fischer.private@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
moritz@pure-entropy.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] of: Fix issue where code would fall through to error case.
Date: Tue, 29 Nov 2016 07:55:17 -0800 [thread overview]
Message-ID: <20161129155517.GA23667@live.com> (raw)
In-Reply-To: <CAL_Jsq+eQYGq7ZtiQaerBk1SP=K1Wgd+b_2UGKFoRS4_s_8Fvg@mail.gmail.com>
Hi Rob,
On Tue, Nov 29, 2016 at 09:06:08AM -0600, Rob Herring wrote:
> On Mon, Nov 28, 2016 at 9:30 AM, Frank Rowand <frowand.list@gmail.com> wrote:
> > On 11/26/16 13:39, Frank Rowand wrote:
> >> On 11/23/16 13:58, Rob Herring wrote:
> >>> On Thu, Nov 17, 2016 at 6:10 PM, Moritz Fischer
> >>> <moritz.fischer.private@gmail.com> wrote:
> >>>> On Thu, Nov 17, 2016 at 4:02 PM, Frank Rowand <frowand.list@gmail.com> wrote:
> >>>>> On 11/17/16 15:40, Frank Rowand wrote:
> >>>>>> On 11/17/16 15:25, Moritz Fischer wrote:
> >>>>>>> No longer fall through into the error case that prints out
> >>>>>>> an error if no error (err = 0) occurred.
> >>>>>>>
> >>>>>>> Fixes d9181b20a83(of: Add back an error message, restructured)
> >>>>>>> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
> >>>>>>> ---
> >>>>>>> drivers/of/resolver.c | 6 +++++-
> >>>>>>> 1 file changed, 5 insertions(+), 1 deletion(-)
> >>>>>>>
> >>>>>>> diff --git a/drivers/of/resolver.c b/drivers/of/resolver.c
> >>>>>>> index 783bd09..785076d 100644
> >>>>>>> --- a/drivers/of/resolver.c
> >>>>>>> +++ b/drivers/of/resolver.c
> >>>>>>> @@ -358,9 +358,13 @@ int of_resolve_phandles(struct device_node *overlay)
> >>>>>>>
> >>>>>>> err = update_usages_of_a_phandle_reference(overlay, prop, phandle);
> >>>>>>> if (err)
> >>>>>>> - break;
> >>>>>>> + goto err_out;
> >>>>>>> }
> >>>>>>>
> >>>>>>> + of_node_put(tree_symbols);
> >>>>>>> +
> >>>>>>> + return 0;
> >>>>>>> +
> >>>>>>> err_out:
> >>>>>>> pr_err("overlay phandle fixup failed: %d\n", err);
> >>>>>>> out:
> >>>>>>
> >>>>>> Thanks for catching that.
> >>>>>>
> >>>>>> Rob, please apply.
> >>>>>>
> >>>>>> Reviewed-by: Frank Rowand <frank.rowand@am.sony.com>
> >>>>>>
> >>>>>> -Frank
> >>>>>
> >>>>> On second thought, isn't the common pattern when clean up is needed for
> >>>>> both the no-error path and the error path something like:
> >>>>>
> >>>>>
> >>>>> out:
> >>>>> of_node_put(tree_symbols);
> >>>>> return err;
> >>>>>
> >>>>> err_out:
> >>>>> pr_err("overlay phandle fixup failed: %d\n", err);
> >>>>> goto out;
> >>>>> }
> >>>>>
> >>>>>
> >>>>> I don't have a strong opinion, whatever Rob wants to take is fine with me.
> >>>>
> >>>> Same here. I tried to avoid the jumping back part, but if that's the
> >>>> common pattern,
> >>>> I can submit a v2 doing that instead.
> >>>
> >>> Both are ugly. Just do:
> >>>
> >>> if (err)
> >>> pr_err(...);
> >>>
> >>> Rob
> >>
> >> Agreed. Thanks for the touch of sanity Rob.
> >>
> >> -Frank
> >
> > I succumbed to looking only at the few lines of code above and not the
> > fuller context of the file that the patch applies to.
> >
> > The proposed patch was fixing the problem that a normal completion
> > of the for loop was falling through into the err_out label. So what
> > looks cleaner ("if (err) pr_err(...)") is actually not correct.
>
> What!? The *only* problem was printing the error message in the err=0
> case. All that needs to be fixed is not doing that. If we do that,
> then we really only need 1 goto label.
I think you're right. Can you look at my v3 that I sent. I also tried to
fix cases where we can just do
return 0;
vs.
err = 0;
goto err
...
err:
of_node_put(NULL /*tree_symbols is NULL*/);
return err;
Thanks,
Moritz
next prev parent reply other threads:[~2016-11-29 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 23:25 [PATCH] of: Fix issue where code would fall through to error case Moritz Fischer
2016-11-17 23:40 ` Frank Rowand
2016-11-18 0:02 ` Frank Rowand
2016-11-18 0:10 ` Moritz Fischer
2016-11-23 21:58 ` Rob Herring
2016-11-26 21:39 ` Frank Rowand
2016-11-28 15:30 ` Frank Rowand
2016-11-29 15:06 ` Rob Herring
2016-11-29 15:55 ` Moritz Fischer [this message]
2016-11-29 16:52 ` Frank Rowand
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=20161129155517.GA23667@live.com \
--to=moritz.fischer@ettus.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer.private@gmail.com \
--cc=moritz@pure-entropy.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@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 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).