From: Eugene Loh <eugene.loh@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH 3/3] cg: fix masking of lower 32 bits
Date: Tue, 23 Sep 2025 18:30:08 -0400 [thread overview]
Message-ID: <f972089f-e2d6-13a6-ef53-bdca98472db5@oracle.com> (raw)
In-Reply-To: <SJ0PR10MB567238056385C0BCE6329EECC21DA@SJ0PR10MB5672.namprd10.prod.outlook.com>
On 9/23/25 17:05, Kris Van Hees via DTrace-devel wrote:
> The "and %r0, 0xffffffff' instruction does not actually mask off the
> lower 32 bits as one would expect because 0xffffffff is interpreted as
> -1 and then sign-extedned to a 64-bit value, i.e. keeping all bits.
s/extedned/extended/
> The "mov32 %r0, %r0" instruxtion does correctly mask off the lwoer 32
s/instruxtion/instruction/
s/lwoer/lower/
I started looking at this a while back and was not convinced that the
lower 32 bits were what we want. Do we want them, and do we have a test
that confirms? Or do we want the upper 32 bits? I got distracted and
mothballed the whole thing, but the test involved spawning a child
thread and then looking at its ustack()... maybe after the child had
exited but before the parent did. Admittedly, I was confused at the
time, and I'm even worse now.
> bits because it forced the value in %r0 to be a 32-bit value.
>
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
> ---
> include/bpf_asm.h | 11 +++++++++++
> libdtrace/dt_cg.c | 3 ++-
> 2 files changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/include/bpf_asm.h b/include/bpf_asm.h
> index 152d2312..63987e01 100644
> --- a/include/bpf_asm.h
> +++ b/include/bpf_asm.h
> @@ -36,6 +36,15 @@
> .imm = 0 \
> })
>
> +#define BPF_ALU32_REG(op, dst, src) \
> + ((struct bpf_insn) { \
> + .code = BPF_ALU | (op) | BPF_X, \
> + .dst_reg = (dst), \
> + .src_reg = (src), \
> + .off = 0, \
> + .imm = 0 \
> + })
> +
> #define BPF_END_REG(sz, dst, dir) \
> ((struct bpf_insn) { \
> .code = BPF_ALU | BPF_END | (dir), \
> @@ -68,6 +77,8 @@
> #define BPF_MOV_REG(dst, src) BPF_ALU64_REG(BPF_MOV, dst, src)
> #define BPF_MOV_IMM(dst, val) BPF_ALU64_IMM(BPF_MOV, dst, val)
>
> +#define BPF_MOV32_REG(dst, src) BPF_ALU32_REG(BPF_MOV, dst, src)
> +
> #define BPF_LOAD(sz, dst, src, ofs) \
> ((struct bpf_insn) { \
> .code = BPF_LDX | BPF_MEM | (sz), \
> diff --git a/libdtrace/dt_cg.c b/libdtrace/dt_cg.c
> index a8f2c9d2..28b7e7c4 100644
> --- a/libdtrace/dt_cg.c
> +++ b/libdtrace/dt_cg.c
> @@ -2757,7 +2757,8 @@ dt_cg_act_stack_sub(dt_pcb_t *pcb, dt_node_t *dnp, int reg, int off, dtrace_actk
> dt_regset_xalloc(drp, BPF_REG_0);
> emit(dlp, BPF_CALL_HELPER(BPF_FUNC_get_current_pid_tgid));
> dt_regset_free_args(drp);
> - emit(dlp, BPF_ALU64_IMM(BPF_AND, BPF_REG_0, 0xffffffff));
> + /* mov32 %r0, %r0 effectively masks the lower 32 bits. */
> + emit(dlp, BPF_MOV32_REG(BPF_REG_0, BPF_REG_0));
> emit(dlp, BPF_STORE(BPF_DW, reg, off, BPF_REG_0));
> dt_regset_free(drp, BPF_REG_0);
> }
next prev parent reply other threads:[~2025-09-23 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 21:05 [PATCH 3/3] cg: fix masking of lower 32 bits Kris Van Hees
2025-09-23 22:30 ` Eugene Loh [this message]
2025-09-24 1:28 ` [DTrace-devel] " Kris Van Hees
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=f972089f-e2d6-13a6-ef53-bdca98472db5@oracle.com \
--to=eugene.loh@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.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.