From: Peter Zijlstra <peterz@infradead.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrii Nakryiko <andrii@kernel.org>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Jiri Olsa <jolsa@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Paulo Andrade <pandrade@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86/uprobes: Fix XOL allocation failure for 32-bit tasks
Date: Mon, 12 Jan 2026 17:40:01 +0100 [thread overview]
Message-ID: <20260112164001.GQ830755@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <aWO7Fdxn39piQnxu@redhat.com>
On Sun, Jan 11, 2026 at 04:00:37PM +0100, Oleg Nesterov wrote:
> This script
>
> #!/usr/bin/bash
>
> echo 0 > /proc/sys/kernel/randomize_va_space
>
> echo 'void main(void) {}' > TEST.c
>
> # -fcf-protection to ensure that the 1st endbr32 insn can't be emulated
> gcc -m32 -fcf-protection=branch TEST.c -o test
>
> bpftrace -e 'uprobe:./test:main {}' -c ./test
>
> "hangs", the probed ./test task enters an endless loop.
>
> The problem is that with randomize_va_space == 0
> get_unmapped_area(TASK_SIZE - PAGE_SIZE) called by xol_add_vma() can not
> just return the "addr == TASK_SIZE - PAGE_SIZE" hint, this addr is used
> by the stack vma.
>
> arch_get_unmapped_area_topdown() doesn't take TIF_ADDR32 into account and
> in_32bit_syscall() is false, this leads to info.high_limit > TASK_SIZE.
> vm_unmapped_area() happily returns the high address > TASK_SIZE and then
> get_unmapped_area() returns -ENOMEM after the "if (addr > TASK_SIZE - len)"
> check.
>
> handle_swbp() doesn't report this failure (probably it should) and silently
> restarts the probed insn. Endless loop.
>
> I think that the right fix should change the x86 get_unmapped_area() paths
> to rely on TIF_ADDR32 rather than in_32bit_syscall(). Note also that if
> CONFIG_X86_X32_ABI=y, in_x32_syscall() falsely returns true in this case
> because ->orig_ax = -1.
>
> But we need a simple fix for -stable, so this patch just sets TS_COMPAT if
> the probed task is 32-bit to make in_ia32_syscall() true.
>
> Cc: stable@vger.kernel.org
> Reported-by: Paulo Andrade <pandrade@redhat.com>
> Link: https://lore.kernel.org/all/aV5uldEvV7pb4RA8@redhat.com/
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Does this want a Fixes tag? Or has this been busted like forever?
next prev parent reply other threads:[~2026-01-12 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 14:32 [BUG] x86: 32-bit uprobes are broken Oleg Nesterov
2026-01-07 15:27 ` Peter Zijlstra
2026-01-07 15:52 ` Oleg Nesterov
2026-01-10 15:37 ` Oleg Nesterov
2026-01-11 15:00 ` [PATCH] x86/uprobes: Fix XOL allocation failure for 32-bit tasks Oleg Nesterov
2026-01-12 16:40 ` Peter Zijlstra [this message]
2026-01-12 17:40 ` Oleg Nesterov
2026-01-14 13:10 ` Oleg Nesterov
2026-01-15 21:43 ` [tip: perf/core] " tip-bot2 for Oleg Nesterov
2026-01-16 10:00 ` Oleg Nesterov
2026-01-16 10:41 ` Peter Zijlstra
2026-01-16 10:49 ` tip-bot2 for Oleg Nesterov
2026-01-16 15:27 ` tip-bot2 for Oleg Nesterov
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=20260112164001.GQ830755@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrii@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david@kernel.org \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=pandrade@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome