From: Mike Rapoport <rppt@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Mike Rapoport <rppt@gmail.com>, Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
kernel test robot <lkp@intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] sh: kprobes: remove unused variables in kprobe_exceptions_notify()
Date: Mon, 19 May 2025 13:01:55 +0300 [thread overview]
Message-ID: <aCsBk6OUnkKGSJm3@kernel.org> (raw)
In-Reply-To: <CAMuHMdURQWHY2hAe+_sA8cVh1ERD4EfvJqg=NZDA0iXW-sBX+A@mail.gmail.com>
On Mon, May 19, 2025 at 10:48:20AM +0200, Geert Uytterhoeven wrote:
> Hi Mike,
>
> On Sat, 17 May 2025 at 11:30, Mike Rapoport <rppt@kernel.org> wrote:
> > From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
> >
> > kbuild reports the following warning:
> >
> > arch/sh/kernel/kprobes.c: In function 'kprobe_exceptions_notify':
> > >> arch/sh/kernel/kprobes.c:412:24: warning: variable 'p' set but not used [-Wunused-but-set-variable]
> > 412 | struct kprobe *p = NULL;
> > | ^
> >
> > The variable 'p' is indeed unused since the commit fa5a24b16f94
> > ("sh/kprobes: Don't call the ->break_handler() in SH kprobes code")
> >
> > Remove that variable along with 'kprobe_opcode_t *addr' which also
> > becomes unused after 'p' is removed.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202505151341.EuRFR22l-lkp@intel.com/
> > Fixes: fa5a24b16f94 ("sh/kprobes: Don't call the ->break_handler() in SH kprobes code")
> > Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>
> Thanks for your patch!
>
> "p" and "addr" are definitely unused (besides side-effects?), so
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> > --- a/arch/sh/kernel/kprobes.c
> > +++ b/arch/sh/kernel/kprobes.c
> > @@ -404,13 +404,10 @@ int __kprobes kprobe_fault_handler(struct pt_regs *regs, int trapnr)
> > int __kprobes kprobe_exceptions_notify(struct notifier_block *self,
> > unsigned long val, void *data)
> > {
> > - struct kprobe *p = NULL;
> > struct die_args *args = (struct die_args *)data;
> > int ret = NOTIFY_DONE;
> > - kprobe_opcode_t *addr = NULL;
> > struct kprobe_ctlblk *kcb = get_kprobe_ctlblk();
> >
> > - addr = (kprobe_opcode_t *) (args->regs->pc);
> > if (val == DIE_TRAP &&
> > args->trapnr == (BREAKPOINT_INSTRUCTION & 0xff)) {
> > if (!kprobe_running()) {
> > @@ -421,7 +418,6 @@ int __kprobes kprobe_exceptions_notify(struct notifier_block *self,
> > ret = NOTIFY_DONE;
> > }
> > } else {
> > - p = get_kprobe(addr);
> > if ((kcb->kprobe_status == KPROBE_HIT_SS) ||
> > (kcb->kprobe_status == KPROBE_REENTER)) {
> > if (post_kprobe_handler(args->regs))
>
> I have no idea what this code is supposed to do, and if it actually
> works. Red flags are that the assigned "p" was never used at all
> since the inception of this function.
"p" was used before fa5a24b16f94 ("sh/kprobes: Don't call the
->break_handler() in SH kprobes code"), but I can't say I understand that
code either :)
CC'ing Masami, he probably knows what this code does.
> Gr{oetje,eeting}s,
>
> Geert
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-05-19 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 9:30 [PATCH] sh: kprobes: remove unused variables in kprobe_exceptions_notify() Mike Rapoport
2025-05-19 8:48 ` Geert Uytterhoeven
2025-05-19 10:01 ` Mike Rapoport [this message]
2025-05-19 10:39 ` Geert Uytterhoeven
2025-06-07 13:10 ` John Paul Adrian Glaubitz
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=aCsBk6OUnkKGSJm3@kernel.org \
--to=rppt@kernel.org \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mhiramat@kernel.org \
--cc=rppt@gmail.com \
--cc=ysato@users.sourceforge.jp \
/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