[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5070743.31r3eYUQgx@7950hx>
Date: Fri, 19 Dec 2025 20:27:37 +0800
From: Menglong Dong <menglong.dong@...ux.dev>
To: Andreas Schwab <schwab@...ux-m68k.org>
Cc: Menglong Dong <menglong8.dong@...il.com>, ast@...nel.org,
rostedt@...dmis.org, daniel@...earbox.net, john.fastabend@...il.com,
andrii@...nel.org, martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, mhiramat@...nel.org,
mark.rutland@....com, mathieu.desnoyers@...icios.com, jiang.biao@...ux.dev,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject:
Re: [PATCH bpf-next v3 3/6] bpf: fix the usage of BPF_TRAMP_F_SKIP_FRAME
On 2025/12/19 19:41, Andreas Schwab wrote:
> On Dez 19 2025, Menglong Dong wrote:
>
> > BPF_TRAMP_F_ORIG_STACK
>
> How can that ever be set?
Oops, my bad! It should be BPF_TRAMP_F_CALL_ORIG here. I think
it is some kind of copy-paste mistake. I'll send a fix for it.
Thanks!
Menglong Dong
>
> if (flags & (BPF_TRAMP_F_ORIG_STACK | BPF_TRAMP_F_SHARE_IPMODIFY))
> return -ENOTSUPP;
>
>
Powered by blists - more mailing lists