From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: ytcoode@gmail.com
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com,
rostedt@goodmis.org, Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: [PATCH] tracing: Remove redundant assignment to variable ret'
Date: Mon, 17 Jan 2022 08:41:17 +0100 [thread overview]
Message-ID: <20220117074117.3770-1-lukas.bulwahn@gmail.com> (raw)
In-Reply-To: <20220116144805.102999-1-ytcoode@gmail.com>
Dear Yuntao,
when you consider removing dead-store assignments guided by some static
analyzer, you need to check if the code you are looking at is actually
missing an error-handling branch.
In this case, ftrace_process_locs() may return -ENOMEM, and the caller
needs to appropriately deal with this error return code. Your patch
does not change the code at all, i.e., the compiled object code is the
same as after the patch as before.
Think about how to deal appropriately with the -ENOMEM return in this
caller and submit a patch that implements the right error-handling
branch or argue in your commit message why that is not needed at all.
If you do not understand or cannot check such basic code properties for
dead-store assignments, it might be better to work on some other aspect
and area of the kernel repository. E.g., the kernel documentation build
also has a few warnings that deserve patches to be fixed.
Best regards,
Lukas
next prev parent reply other threads:[~2022-01-17 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 14:48 [PATCH] tracing: Remove redundant assignment to variable ret Yuntao Wang
2022-01-17 7:41 ` Lukas Bulwahn [this message]
2022-01-19 4:17 ` Yuntao Wang
2022-01-19 7:15 ` Lukas Bulwahn
2022-01-19 14:57 ` Steven Rostedt
2022-01-20 6:59 ` [PATCH v2] tracing: Deal with error return code of the ftrace_process_locs() function Yuntao Wang
2022-05-24 17:24 ` Steven Rostedt
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=20220117074117.3770-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=ytcoode@gmail.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
Powered by JetHome