Linux Perf Users
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Andrii Nakryiko <andrii.nakryiko@gmail.com>,
	Breno Leitao <leitao@debian.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org, kernel-team@meta.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] uprobes: Fix NULL pointer dereference in hprobe_expire()
Date: Fri, 31 Jul 2026 10:51:29 +0200	[thread overview]
Message-ID: <20260731085129.GG776954@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <amxgF3S7jfmjHvPv@redhat.com>

On Fri, Jul 31, 2026 at 10:43:03AM +0200, Oleg Nesterov wrote:
> On 07/31, Peter Zijlstra wrote:
> >
> > On Fri, Jul 31, 2026 at 09:56:52AM +0900, Masami Hiramatsu wrote:
> > > On Thu, 30 Jul 2026 12:38:24 +0200
> > >
> > > Either way works. Can we update MAINTAINERS file if you will maintain
> > > uprobe in tip tree?
> >
> > Well it is in kernel/events/ which MAINTAINERS should already assign to
> > me, no?
> 
> Confused... you are already listed as a maintainer. From MAINTAINERS:
> 
> 	UPROBES
> 	M:	Masami Hiramatsu <mhiramat@kernel.org>
> 	M:	Oleg Nesterov <oleg@redhat.com>
> 	M:	Peter Zijlstra <peterz@infradead.org>
> 	L:	linux-kernel@vger.kernel.org
> 	L:	linux-trace-kernel@vger.kernel.org
> 	S:	Maintained
> 	F:	arch/*/include/asm/uprobes.h
> 	F:	arch/*/kernel/probes/uprobes.c
> 	F:	arch/*/kernel/uprobes.c
> 	F:	include/linux/uprobes.h
> 	F:	kernel/events/uprobes.c

Yes, but the 'PERFORMANCE EVENTS SUBSYSTEM' entry will also cover this.
So I have it twice ;-)

PERFORMANCE EVENTS SUBSYSTEM
...
F:      kernel/events/*

Anyway, patch should be in tip/perf/urgent now.

      reply	other threads:[~2026-07-31  8:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 14:44 [PATCH] uprobes: Fix NULL pointer dereference in hprobe_expire() Breno Leitao
2026-07-29 16:02 ` Oleg Nesterov
2026-07-29 19:31   ` Andrii Nakryiko
2026-07-29 23:54     ` Masami Hiramatsu
2026-07-30 10:38       ` Peter Zijlstra
2026-07-31  0:56         ` Masami Hiramatsu
2026-07-31  8:30           ` Peter Zijlstra
2026-07-31  8:43             ` Oleg Nesterov
2026-07-31  8:51               ` Peter Zijlstra [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=20260731085129.GG776954@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=oleg@redhat.com \
    --cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox