All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>,
	Ze Gao <zegao2021@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] probes: Fixes for 6.4-rc1
Date: Thu, 18 May 2023 22:44:09 +0900	[thread overview]
Message-ID: <20230518224409.62cf8ccef515cbccf07f0e13@kernel.org> (raw)

Hi Linus,

Probes fixes for 6.4-rc1:

- Initialize 'ret' local variables on fprobe_handler() to fix the smatch
  warning. With this, fprobe function exit handler is not working
  randomly.

- Fix to use preempt_enable/disable_notrace for rethook handler to
  prevent recursive call of fprobe exit handler (which is based on
  rethook)

- Fix recursive call issue on fprobe_kprobe_handler().

- Fix to detect recursive call on fprobe_exit_handler().

- Fix to make all arch-dependent rethook code notrace.
  (the arch-independent code is already notrace)


Please pull the latest probes-fixes-v6.4-rc1 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-fixes-v6.4-rc1

Tag SHA1: edaa9b59161d819661ea96a97850d9aaf6d43bdc
Head SHA1: 571a2a50a8fc546145ffd3bf673547e9fe128ed2


Masami Hiramatsu (Google) (1):
      tracing: fprobe: Initialize ret valiable to fix smatch error

Ze Gao (4):
      rethook: use preempt_{disable, enable}_notrace in rethook_trampoline_handler
      fprobe: make fprobe_kprobe_handler recursion free
      fprobe: add recursion detection in fprobe_exit_handler
      rethook, fprobe: do not trace rethook related functions

----
 arch/riscv/kernel/probes/Makefile |  2 ++
 arch/s390/kernel/Makefile         |  1 +
 arch/x86/kernel/Makefile          |  1 +
 kernel/trace/fprobe.c             | 73 +++++++++++++++++++++++++++++++--------
 kernel/trace/rethook.c            |  4 +--
 5 files changed, 64 insertions(+), 17 deletions(-)


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

             reply	other threads:[~2023-05-18 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 13:44 Masami Hiramatsu [this message]
2023-05-18 16:10 ` [GIT PULL] probes: Fixes for 6.4-rc1 pr-tracker-bot

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=20230518224409.62cf8ccef515cbccf07f0e13@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zegao2021@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 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.