mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Leo Yan <leo.yan@arm.com>, Mikel Rychliski <mikel@mikelr.com>,
	Viktor Malik <vmalik@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: [GIT PULL] probes: Fixes for v6.12-rc4-2
Date: Wed, 23 Oct 2024 23:36:00 +0900	[thread overview]
Message-ID: <20241023233600.d309ab5fa8421e97d041bbc0@kernel.org> (raw)

Hi Linus,

Probes fixes for v6.12-rc4(2):

- objpool: Fix choosing allocation for percpu slots
  Fixes to allocate objpool's percpu slots correctly according to the
  GFP flag. It checks whether "any bit" in GFP_ATOMIC is set to choose
  the vmalloc source, but it should check "all bits" in GFP_ATOMIC flag
  is set, because GFP_ATOMIC is a combined flag.

- tracing/probes: Fix MAX_TRACE_ARGS limit handling
  If more than MAX_TRACE_ARGS are passed for creating a probe event, the
  entries over MAX_TRACE_ARG in trace_arg array are not initialized.
  Thus if the kernel accesses those entries, it crashes. This rejects
  creating event if the number of arguments is over MAX_TRACE_ARGS.

- tracing: Consider the NULL character when validating the event length
  A strlen() is used when parsing the event name, and the original code
  does not consider the terminal null byte. Thus it can pass the name
  1 byte longer than the buffer. This fixes to check it correctly.


Please pull the latest probes-fixes-v6.12-rc4.2 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-fixes-v6.12-rc4.2

Tag SHA1: 62eeda86599cd8c8fe92b4bc6181ef6d2c1e6e03
Head SHA1: 0b6e2e22cb23105fcb171ab92f0f7516c69c8471


Leo Yan (1):
      tracing: Consider the NULL character when validating the event length

Mikel Rychliski (1):
      tracing/probes: Fix MAX_TRACE_ARGS limit handling

Viktor Malik (1):
      objpool: fix choosing allocation for percpu slots

----
 kernel/trace/trace_eprobe.c | 7 ++++++-
 kernel/trace/trace_fprobe.c | 6 +++++-
 kernel/trace/trace_kprobe.c | 6 +++++-
 kernel/trace/trace_probe.c  | 2 +-
 kernel/trace/trace_uprobe.c | 4 +++-
 lib/objpool.c               | 2 +-
 6 files changed, 21 insertions(+), 6 deletions(-)

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

             reply	other threads:[~2024-10-23 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 14:36 Masami Hiramatsu [this message]
2024-10-24 21:05 ` Linus Torvalds
2024-10-25  3:09   ` Masami Hiramatsu
2024-10-24 21:29 ` 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=20241023233600.d309ab5fa8421e97d041bbc0@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikel@mikelr.com \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vmalik@redhat.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

all inboxes | Powered by JetHome®