From: Sumanth Korikkar <sumanthk@linux.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
sumanthk@linux.ibm.com
Subject: [PATCH] uprobes: Skip breakpoint installation on non executable vmas
Date: Wed, 5 Aug 2026 15:19:04 +0200 [thread overview]
Message-ID: <20260805131904.1127416-1-sumanthk@linux.ibm.com> (raw)
bpftrace -e 'usdt:./testprogs/usdt_semaphore_test:tracetest:testprobe {
printf("%s\n", str(arg1) ); exit(); }'
expects a semaphore increment of 1, but semaphore gets double incremented
Test program:
https://github.com/bpftrace/bpftrace/blob/master/tests/testprogs/usdt_semaphore_test.c
Reason: .text mapping and RELRO mapping resolve to the same page aligned
file offset 0
01000000-01001000 r-xp 00000000 5e:01 usdt_semaphore_test (.text)
01001000-01002000 r--p 00000000 5e:01 usdt_semaphore_test (RELRO)
01002000-01003000 rw-p 00001000 5e:01 usdt_semaphore_test (semaphore)
valid_vma() currently accepts both mappings (which contains executable
text and RELRO mapping) during uprobe registration, since both have
VM_MAYEXEC set. This causes register_for_each_vma() to call
install_breakpoint() twice for the same underlying uprobe offset in the
process. This means, update_ref_ctr() is called twice for the same
process, so a usdt semaphore is incremented from 0 to 2.
Installing a breakpoint for mapping without VM_EXEC and
updating usdt reference counter in that case is not useful.
Skip non VM_EXEC mappings in install_breakpoint(). This fixes semaphore
double increment as shown in the above usecase.
Signed-off-by: Sumanth Korikkar <sumanthk@linux.ibm.com>
---
kernel/events/uprobes.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
index 6300b216012c..9e0bbc3cf401 100644
--- a/kernel/events/uprobes.c
+++ b/kernel/events/uprobes.c
@@ -1155,6 +1155,9 @@ static int install_breakpoint(struct uprobe *uprobe, struct vm_area_struct *vma,
bool first_uprobe;
int ret;
+ if (!(vma->vm_flags & VM_EXEC))
+ return 0;
+
ret = prepare_uprobe(uprobe, vma->vm_file, mm, vaddr);
if (ret)
return ret;
--
2.53.0
next reply other threads:[~2026-08-05 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 13:19 Sumanth Korikkar [this message]
2026-08-05 15:14 ` [PATCH] uprobes: Skip breakpoint installation on non executable vmas Oleg Nesterov
2026-08-05 17:29 ` Andrii Nakryiko
2026-08-05 18:26 ` Oleg Nesterov
2026-08-05 21:29 ` Sumanth Korikkar
2026-08-05 22:05 ` Sumanth Korikkar
2026-08-05 21:06 ` Sumanth Korikkar
2026-08-06 11:01 ` Oleg Nesterov
2026-08-06 13:34 ` Sumanth Korikkar
2026-08-06 15:35 ` Oleg Nesterov
2026-08-06 20:42 ` Andrii Nakryiko
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=20260805131904.1127416-1-sumanthk@linux.ibm.com \
--to=sumanthk@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=oleg@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 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.