From: Leon Hwang <hffilwlqm@gmail.com>
To: ast@kernel.org
Cc: daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
hawk@kernel.org, hffilwlqm@gmail.com, tangyeechou@gmail.com,
kernel-patches-bot@fb.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH bpf-next v2 0/2] bpf: Introduce user log
Date: Sat, 8 Jul 2023 12:07:48 +0800 [thread overview]
Message-ID: <20230708040750.72570-1-hffilwlqm@gmail.com> (raw)
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().
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
next reply other threads:[~2023-07-08 4:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 4:07 Leon Hwang [this message]
2023-07-08 4:07 ` [PATCH bpf-next v2 1/2] bpf: Introduce bpf generic log Leon Hwang
2023-07-10 22:23 ` Andrii Nakryiko
2023-07-11 3:10 ` Leon Hwang
2023-07-08 4:07 ` [PATCH bpf-next v2 2/2] bpf: Introduce bpf user log Leon Hwang
2023-07-10 23:45 ` Alexei Starovoitov
2023-07-11 2:55 ` Leon Hwang
2023-07-08 22:02 ` [PATCH bpf-next v2 0/2] bpf: Introduce " Daniel Xu
2023-07-09 3:44 ` Leon Hwang
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=20230708040750.72570-1-hffilwlqm@gmail.com \
--to=hffilwlqm@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel-patches-bot@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tangyeechou@gmail.com \
--cc=yhs@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®