diff options
author | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-07-25 22:28:56 -0400 |
---|---|---|
committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-07-25 22:33:50 -0400 |
commit | 2519c1bbe38d7acacc9aacba303ca6f97482ed53 (patch) | |
tree | 6d60632f0a1cbd4fb9a9c79462e6a0887bd4c19a /net/smc | |
parent | 15cc78644d0075e76d59476a4467e7143860f660 (diff) | |
download | linux-2519c1bbe38d7acacc9aacba303ca6f97482ed53.tar.gz linux-2519c1bbe38d7acacc9aacba303ca6f97482ed53.tar.bz2 linux-2519c1bbe38d7acacc9aacba303ca6f97482ed53.zip |
tracing: Quiet gcc warning about maybe unused link variable
Commit 57ea2a34adf4 ("tracing/kprobes: Fix trace_probe flags on
enable_trace_kprobe() failure") added an if statement that depends on another
if statement that gcc doesn't see will initialize the "link" variable and
gives the warning:
"warning: 'link' may be used uninitialized in this function"
It is really a false positive, but to quiet the warning, and also to make
sure that it never actually is used uninitialized, initialize the "link"
variable to NULL and add an if (!WARN_ON_ONCE(!link)) where the compiler
thinks it could be used uninitialized.
Cc: stable@vger.kernel.org
Fixes: 57ea2a34adf4 ("tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure")
Reported-by: kbuild test robot <lkp@intel.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'net/smc')
0 files changed, 0 insertions, 0 deletions