From: John Kacur <jkacur@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Daniel Bristot de Oliveira <bristot@kernel.org>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Clark Williams <williams@redhat.com>,
linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] rtla/osnoise: prevent NULL dereference in error handling
Date: Fri, 9 Aug 2024 14:42:13 -0400 (EDT) [thread overview]
Message-ID: <25b597bd-bdc4-411f-e5d9-78ed4d042c4b@redhat.com> (raw)
In-Reply-To: <20240809140545.698f654e@gandalf.local.home>
On Fri, 9 Aug 2024, Steven Rostedt wrote:
> On Fri, 9 Aug 2024 13:53:33 -0400 (EDT)
> John Kacur <jkacur@redhat.com> wrote:
>
>
> > > > Although your fix appears to be correct, I wonder if it would be better to
> > > > create a second error label, such as out_destroy_tool: as described in
> > > > section 7 of the coding-style.rst
> > > >
> > >
> > > There's no reason for that. It's the only error path. That is, nothing
> > > would jump to the original out_err:
> > >
> > > And for a single error, an if statement is good enough.
> > >
> > > -- Steve
> > >
> > >
> >
> > Ah, right of course.
> > Okay in that case, Signed-off-by: John Kacur <jkacur@redhat.com>
> > (applied the patch, built and ran)
>
> Note, "Signed-off-by" is for the author of a patch or someone pushing it
> through their tree. I believe you want either "Acked-by" or "Reviewed-by",
> and since you ran it you could also add "Tested-by".
>
> -- Steve
Thanks Steve,
Reviewed-by: John Kacur <jkacur@redhat.com>
Tested-by: John Kacur <jkacur@redhat.com>
next prev parent reply other threads:[~2024-08-09 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 12:34 [PATCH] rtla/osnoise: prevent NULL dereference in error handling Dan Carpenter
2024-08-09 17:34 ` John Kacur
2024-08-09 17:41 ` Steven Rostedt
2024-08-09 17:53 ` John Kacur
2024-08-09 18:05 ` Steven Rostedt
2024-08-09 18:42 ` John Kacur [this message]
2024-08-12 12:45 ` Luis Claudio R. Goncalves
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=25b597bd-bdc4-411f-e5d9-78ed4d042c4b@redhat.com \
--to=jkacur@redhat.com \
--cc=bristot@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=williams@redhat.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