[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230801150826.6f617919@kernel.org>
Date: Tue, 1 Aug 2023 15:08:26 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Leon Hwang <hffilwlqm@...il.com>
Cc: bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
john.fastabend@...il.com, andrii@...nel.org, martin.lau@...ux.dev,
song@...nel.org, yonghong.song@...ux.dev, kpsingh@...nel.org,
sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
hawk@...nel.org, rostedt@...dmis.org, mhiramat@...nel.org,
mykolal@...com, shuah@...nel.org, tangyeechou@...il.com,
kernel-patches-bot@...com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org
Subject: Re: [PATCH bpf-next v5 1/2] bpf, xdp: Add tracepoint to xdp
attaching failure
On Tue, 1 Aug 2023 22:26:20 +0800 Leon Hwang wrote:
> When error happens in dev_xdp_attach(), it should have a way to tell
> users the error message like the netlink approach.
>
> To avoid breaking uapi, adding a tracepoint in bpf_xdp_link_attach() is
> an appropriate way to notify users the error message.
>
> Hence, bpf libraries are able to retrieve the error message by this
> tracepoint, and then report the error message to users.
Whatevered-by: Jakub Kicinski <kuba@...nel.org> ?
Powered by blists - more mailing lists