From: Dan Carpenter <dan.carpenter@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] Silence an uninitialized variable warning
Date: Wed, 04 Dec 2019 18:42:47 +0000 [thread overview]
Message-ID: <20191204184247.GG1765@kadam> (raw)
In-Reply-To: <20191204092640.692c95af@gandalf.local.home>
On Wed, Dec 04, 2019 at 09:26:40AM -0500, Steven Rostedt wrote:
> On Tue, 26 Nov 2019 15:19:34 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > Smatch complains that "ret" could be uninitialized if we don't enter the
> > loop. I don't know if that's possible, but it's nicer to return a
> > literal zero instead.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > ---
> > kernel/trace/trace_syscalls.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
> > index 73140d80dd46..63528f458826 100644
> > --- a/kernel/trace/trace_syscalls.c
> > +++ b/kernel/trace/trace_syscalls.c
> > @@ -286,7 +286,7 @@ static int __init syscall_enter_define_fields(struct trace_event_call *call)
> > offset += sizeof(unsigned long);
> > }
> >
> > - return ret;
> > + return 0;
> > }
> >
> > static void ftrace_syscall_enter(void *data, struct pt_regs *regs, long id)
>
> The current code has this:
>
> static int __init syscall_enter_define_fields(struct trace_event_call *call)
> {
> struct syscall_trace_enter trace;
> struct syscall_metadata *meta = call->data;
> int ret;
> int i;
> int offset = offsetof(typeof(trace), args);
>
> ret = trace_define_field(call, SYSCALL_FIELD(int, nr, __syscall_nr),
> FILTER_OTHER);
In linux-next this ret = trace_define_field() assignment is removed.
That was commit 60fdad00827c ("ftrace: Rework event_create_dir()").
> if (ret)
> return ret;
>
> for (i = 0; i < meta->nb_args; i++) {
> ret = trace_define_field(call, meta->types[i],
> meta->args[i], offset,
> sizeof(unsigned long), 0,
> FILTER_OTHER);
> offset += sizeof(unsigned long);
> }
>
> return ret;
> }
>
>
> How can ret possibly be uninitialized?
I should have written this commit more carefully and verified whether
meta->nb_args can actually be zero instead of just assuming it was a
false positive...
regards,
dan carpenter
WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] Silence an uninitialized variable warning
Date: Wed, 4 Dec 2019 21:42:47 +0300 [thread overview]
Message-ID: <20191204184247.GG1765@kadam> (raw)
In-Reply-To: <20191204092640.692c95af@gandalf.local.home>
On Wed, Dec 04, 2019 at 09:26:40AM -0500, Steven Rostedt wrote:
> On Tue, 26 Nov 2019 15:19:34 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> > Smatch complains that "ret" could be uninitialized if we don't enter the
> > loop. I don't know if that's possible, but it's nicer to return a
> > literal zero instead.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > ---
> > kernel/trace/trace_syscalls.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
> > index 73140d80dd46..63528f458826 100644
> > --- a/kernel/trace/trace_syscalls.c
> > +++ b/kernel/trace/trace_syscalls.c
> > @@ -286,7 +286,7 @@ static int __init syscall_enter_define_fields(struct trace_event_call *call)
> > offset += sizeof(unsigned long);
> > }
> >
> > - return ret;
> > + return 0;
> > }
> >
> > static void ftrace_syscall_enter(void *data, struct pt_regs *regs, long id)
>
> The current code has this:
>
> static int __init syscall_enter_define_fields(struct trace_event_call *call)
> {
> struct syscall_trace_enter trace;
> struct syscall_metadata *meta = call->data;
> int ret;
> int i;
> int offset = offsetof(typeof(trace), args);
>
> ret = trace_define_field(call, SYSCALL_FIELD(int, nr, __syscall_nr),
> FILTER_OTHER);
In linux-next this ret = trace_define_field() assignment is removed.
That was commit 60fdad00827c ("ftrace: Rework event_create_dir()").
> if (ret)
> return ret;
>
> for (i = 0; i < meta->nb_args; i++) {
> ret = trace_define_field(call, meta->types[i],
> meta->args[i], offset,
> sizeof(unsigned long), 0,
> FILTER_OTHER);
> offset += sizeof(unsigned long);
> }
>
> return ret;
> }
>
>
> How can ret possibly be uninitialized?
I should have written this commit more carefully and verified whether
meta->nb_args can actually be zero instead of just assuming it was a
false positive...
regards,
dan carpenter
next prev parent reply other threads:[~2019-12-04 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:19 [PATCH] Silence an uninitialized variable warning Dan Carpenter
2019-11-26 12:19 ` Dan Carpenter
2019-12-04 14:26 ` Steven Rostedt
2019-12-04 14:26 ` Steven Rostedt
2019-12-04 18:42 ` Dan Carpenter [this message]
2019-12-04 18:42 ` Dan Carpenter
2019-12-05 9:32 ` Peter Zijlstra
2019-12-05 9:32 ` Peter Zijlstra
2019-12-05 10:02 ` Dan Carpenter
2019-12-05 10:02 ` 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=20191204184247.GG1765@kadam \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.