From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Li zeming <zeming@nfschina.com>
Cc: naveen.n.rao@linux.ibm.com, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] kprobes: Remove unnecessary initial values of variables
Date: Tue, 19 Sep 2023 14:19:04 +0900 [thread overview]
Message-ID: <20230919141904.ef53e6663e4c5400ae913622@kernel.org> (raw)
In-Reply-To: <20230919012823.7815-1-zeming@nfschina.com>
On Tue, 19 Sep 2023 09:28:23 +0800
Li zeming <zeming@nfschina.com> wrote:
> ri and sym is assigned first, so it does not need to initialize the
> assignment.
>
Yes, thanks for fixing!
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> Signed-off-by: Li zeming <zeming@nfschina.com>
> ---
> kernel/kprobes.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/kprobes.c b/kernel/kprobes.c
> index ca385b61d546..82b2a366d496 100644
> --- a/kernel/kprobes.c
> +++ b/kernel/kprobes.c
> @@ -1990,7 +1990,7 @@ NOKPROBE_SYMBOL(__kretprobe_find_ret_addr);
> unsigned long kretprobe_find_ret_addr(struct task_struct *tsk, void *fp,
> struct llist_node **cur)
> {
> - struct kretprobe_instance *ri = NULL;
> + struct kretprobe_instance *ri;
> kprobe_opcode_t *ret;
>
> if (WARN_ON_ONCE(!cur))
> @@ -2817,7 +2817,7 @@ static int show_kprobe_addr(struct seq_file *pi, void *v)
> {
> struct hlist_head *head;
> struct kprobe *p, *kp;
> - const char *sym = NULL;
> + const char *sym;
> unsigned int i = *(loff_t *) v;
> unsigned long offset = 0;
> char *modname, namebuf[KSYM_NAME_LEN];
> --
> 2.18.2
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-09-19 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 1:28 Li zeming
2023-09-19 5:19 ` Masami Hiramatsu [this message]
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=20230919141904.ef53e6663e4c5400ae913622@kernel.org \
--to=mhiramat@kernel.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=zeming@nfschina.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