From: Oleg Nesterov <oleg@redhat.com>
To: Adriano Cordova <adrianox@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.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>
Subject: Re: [PATCH 1/2] uprobes: Use a dedicated mutex to serialize prepare_uprobe()
Date: Sun, 20 Sep 2026 16:35:09 +0200 [thread overview]
Message-ID: <aq_vHbcivZTtKZLN@redhat.com> (raw)
In-Reply-To: <20260918143209.709291-1-adrianox@gmail.com>
On 09/18, Adriano Cordova wrote:
>
> prepare_uprobe() serializes its callers by taking consumer_rwsem for
> writing. That rwsem protects the consumer list, not the instruction
> copy.
>
> Give struct uprobe a dedicated prepare_mutex and use it instead.
>
> No functional change.
So why? Is it preparation for 2/2 ? At first glance it doesn't need
this change... Please add more details.
Oleg.
> Signed-off-by: Adriano Cordova <adrianox@gmail.com>
> ---
> kernel/events/uprobes.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
> index 7709ea882477..686585539ebf 100644
> --- a/kernel/events/uprobes.c
> +++ b/kernel/events/uprobes.c
> @@ -64,6 +64,7 @@ struct uprobe {
> refcount_t ref;
> struct rw_semaphore register_rwsem;
> struct rw_semaphore consumer_rwsem;
> + struct mutex prepare_mutex; /* serializes prepare_uprobe() */
> struct list_head pending_list;
> struct list_head consumers;
> struct inode *inode; /* Also hold a ref to inode */
> @@ -1007,6 +1008,7 @@ static struct uprobe *alloc_uprobe(struct inode *inode, loff_t offset,
> INIT_LIST_HEAD(&uprobe->consumers);
> init_rwsem(&uprobe->register_rwsem);
> init_rwsem(&uprobe->consumer_rwsem);
> + mutex_init(&uprobe->prepare_mutex);
> RB_CLEAR_NODE(&uprobe->rb_node);
> refcount_set(&uprobe->ref, 1);
>
> @@ -1104,8 +1106,8 @@ static int prepare_uprobe(struct uprobe *uprobe, struct file *file,
> if (test_bit(UPROBE_COPY_INSN, &uprobe->flags))
> return ret;
>
> - /* TODO: move this into _register, until then we abuse this sem. */
> - down_write(&uprobe->consumer_rwsem);
> + /* Serialize concurrent prepare_uprobe() calls from uprobe_mmap(). */
> + mutex_lock(&uprobe->prepare_mutex);
> if (test_bit(UPROBE_COPY_INSN, &uprobe->flags))
> goto out;
>
> @@ -1125,7 +1127,7 @@ static int prepare_uprobe(struct uprobe *uprobe, struct file *file,
> set_bit(UPROBE_COPY_INSN, &uprobe->flags);
>
> out:
> - up_write(&uprobe->consumer_rwsem);
> + mutex_unlock(&uprobe->prepare_mutex);
>
> return ret;
> }
> --
> 2.51.0
>
prev parent reply other threads:[~2026-09-20 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 14:32 Adriano Cordova
2026-09-18 14:32 ` [PATCH 2/2] uprobes: Hide unprepared uprobes from the breakpoint paths Adriano Cordova
2026-09-20 14:38 ` Oleg Nesterov
2026-09-20 14:35 ` Oleg Nesterov [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=aq_vHbcivZTtKZLN@redhat.com \
--to=oleg@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=adrianox@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@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=peterz@infradead.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
all inboxes | Powered by JetHome®