[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <v76ytdfdf2sqhdufkqxzsuznandia3x4l4iyghpirxkzytngxq@uttzaebbmdjb>
Date: Sat, 8 Jul 2023 16:02:47 -0600
From: Daniel Xu <dxu@...uu.xyz>
To: Leon Hwang <hffilwlqm@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, john.fastabend@...il.com,
andrii@...nel.org, martin.lau@...ux.dev, song@...nel.org,
yhs@...com, kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com,
jolsa@...nel.org, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, hawk@...nel.org,
tangyeechou@...il.com, kernel-patches-bot@...com,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Introduce user log
Hi Leon,
On Sat, Jul 08, 2023 at 12:07:48PM +0800, Leon Hwang wrote:
> This series introduces bpf user log to transfer error message from
> kernel space to user space when users provide buffer to receive the
> error message.
>
> Especially, when to attach XDP to device, it can transfer the error
> message along with errno from dev_xdp_attach() to user space, if error
> happens in dev_xdp_attach().
Have you considered adding a tracepoint instead? With some TP_printk()
stuff I think you can achieve a similar result without having to do
go through changing uapi.
>
> Leon Hwang (2):
> bpf: Introduce bpf generic log
> bpf: Introduce bpf user log
>
> include/linux/bpf.h | 3 ++
> include/uapi/linux/bpf.h | 8 ++++++
> kernel/bpf/log.c | 52 ++++++++++++++++++++++++++++++++++
> net/core/dev.c | 4 ++-
> tools/include/uapi/linux/bpf.h | 8 ++++++
> 5 files changed, 74 insertions(+), 1 deletion(-)
>
>
> base-commit: 622f876ab3ced325fe3c2363c6e9c128b7e6c73a
> --
> 2.41.0
>
>
Thanks,
Daniel
Powered by blists - more mailing lists