From: Leon Hwang <leon.hwang@linux.dev>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, daniel@iogearbox.net,
Leon Hwang <leon.hwang@linux.dev>
Subject: [RFC PATCH bpf-next v3 04/10] bpf: Add common attr support for prog_load
Date: Thu, 2 Oct 2025 23:48:35 +0800 [thread overview]
Message-ID: <20251002154841.99348-5-leon.hwang@linux.dev> (raw)
In-Reply-To: <20251002154841.99348-1-leon.hwang@linux.dev>
The log buffer of common attributes would be confusing with the one in
'union bpf_attr' for BPF_PROG_LOAD.
In order to clarify the usage of these two log buffers, they both can be
used for logging if:
* They are same, including 'log_buf', 'log_level' and 'log_size'.
* One of them is missing, then another one will be used for logging.
If they both have 'log_buf' but they are not same totally, return -EUSERS.
Signed-off-by: Leon Hwang <leon.hwang@linux.dev>
---
kernel/bpf/syscall.c | 55 ++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 53 insertions(+), 2 deletions(-)
diff --git a/kernel/bpf/syscall.c b/kernel/bpf/syscall.c
index 2bdc0b43ec832..698c30ff99486 100644
--- a/kernel/bpf/syscall.c
+++ b/kernel/bpf/syscall.c
@@ -6092,11 +6092,57 @@ static int prog_stream_read(union bpf_attr *attr)
return ret;
}
-static int copy_prog_load_log_true_size(union bpf_attr *attr, bpfptr_t uattr, unsigned int size)
+static int check_log_attrs(u64 log_buf, u32 log_size, u32 log_level,
+ struct bpf_common_attr *common_attrs)
+{
+ if (log_buf && common_attrs->log_buf && (log_buf != common_attrs->log_buf ||
+ log_size != common_attrs->log_size ||
+ log_level != common_attrs->log_level))
+ return -EUSERS;
+
+ return 0;
+}
+
+static int check_prog_load_log_attrs(union bpf_attr *attr, struct bpf_common_attr *common_attrs,
+ bool *log_common_attrs)
+{
+ int err;
+
+ err = check_log_attrs(attr->log_buf, attr->log_size, attr->log_level, common_attrs);
+ if (err)
+ return err;
+
+ if (!attr->log_buf && common_attrs->log_buf) {
+ *log_common_attrs = true;
+ attr->log_buf = common_attrs->log_buf;
+ attr->log_size = common_attrs->log_size;
+ attr->log_level = common_attrs->log_level;
+ }
+
+ return 0;
+}
+
+static int __copy_common_attr_log_true_size(bpfptr_t uattr, unsigned int size, u32 *log_true_size)
+{
+ if (size >= offsetofend(struct bpf_common_attr, log_true_size) &&
+ copy_to_bpfptr_offset(uattr, offsetof(struct bpf_common_attr, log_true_size),
+ log_true_size, sizeof(*log_true_size)))
+ return -EFAULT;
+
+ return 0;
+}
+
+static int copy_prog_load_log_true_size(union bpf_attr *attr, bpfptr_t uattr, unsigned int size,
+ struct bpf_common_attr *common_attrs, bpfptr_t uattr_common,
+ unsigned int size_common, bool log_common_attrs)
{
if (!attr->log_true_size)
return 0;
+ if (log_common_attrs)
+ return __copy_common_attr_log_true_size(uattr_common, size_common,
+ &attr->log_true_size);
+
if (size >= offsetofend(union bpf_attr, log_true_size) &&
copy_to_bpfptr_offset(uattr, offsetof(union bpf_attr, log_true_size),
&attr->log_true_size, sizeof(attr->log_true_size)))
@@ -6109,6 +6155,7 @@ static int __sys_bpf(enum bpf_cmd cmd, bpfptr_t uattr, unsigned int size,
bpfptr_t uattr_common, unsigned int size_common)
{
struct bpf_common_attr common_attrs;
+ bool log_common_attrs = false;
union bpf_attr attr;
int err, ret;
@@ -6158,9 +6205,13 @@ static int __sys_bpf(enum bpf_cmd cmd, bpfptr_t uattr, unsigned int size,
err = map_freeze(&attr);
break;
case BPF_PROG_LOAD:
+ err = check_prog_load_log_attrs(&attr, &common_attrs, &log_common_attrs);
+ if (err)
+ break;
attr.log_true_size = 0;
err = bpf_prog_load(&attr, uattr);
- ret = copy_prog_load_log_true_size(&attr, uattr, size);
+ ret = copy_prog_load_log_true_size(&attr, uattr, size, &common_attrs, uattr_common,
+ size_common, log_common_attrs);
err = ret ? ret : err;
break;
case BPF_OBJ_PIN:
--
2.51.0
next prev parent reply other threads:[~2025-10-02 15:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 15:48 [RFC PATCH bpf-next v3 00/10] bpf: Extend bpf syscall with common attributes support Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 01/10] " Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 02/10] libbpf: Add support for extended bpf syscall Leon Hwang
2025-10-06 23:08 ` Andrii Nakryiko
2025-10-09 5:15 ` Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 03/10] bpf: Refactor reporting log_true_size for prog_load Leon Hwang
2025-10-02 18:34 ` Alexei Starovoitov
2025-10-03 2:06 ` Leon Hwang
2025-10-02 15:48 ` Leon Hwang [this message]
2025-10-02 23:51 ` [RFC PATCH bpf-next v3 04/10] bpf: Add common attr support " Alexei Starovoitov
2025-10-03 2:25 ` Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 05/10] bpf: Refactor reporting btf_log_true_size for btf_load Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 06/10] bpf: Add common attr support " Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 07/10] bpf: Add warnings for internal bugs in map_create Leon Hwang
2025-10-03 0:06 ` Alexei Starovoitov
2025-10-03 2:31 ` Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 08/10] bpf: Add common attr support for map_create Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 09/10] libbpf: " Leon Hwang
2025-10-06 23:08 ` Andrii Nakryiko
2025-10-09 5:35 ` Leon Hwang
2025-10-02 15:48 ` [RFC PATCH bpf-next v3 10/10] selftests/bpf: Add cases to test map create failure log Leon Hwang
2025-10-03 6:38 ` [syzbot ci] Re: bpf: Extend bpf syscall with common attributes support syzbot ci
2025-10-03 6: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=20251002154841.99348-5-leon.hwang@linux.dev \
--to=leon.hwang@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
/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