bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, andrii@kernel.org,
	john.fastabend@gmail.com, bpf@vger.kernel.org,
	kernel-team@fb.com
Subject: [PATCH v3 bpf-next 02/17] bpf: Introduce bpfptr_t user/kernel pointer.
Date: Wed,  5 May 2021 20:44:50 -0700	[thread overview]
Message-ID: <20210506034505.25979-3-alexei.starovoitov@gmail.com> (raw)
In-Reply-To: <20210506034505.25979-1-alexei.starovoitov@gmail.com>

From: Alexei Starovoitov <ast@kernel.org>

Similar to sockptr_t introduce bpfptr_t with few additions:
make_bpfptr() creates new user/kernel pointer in the same address space as
existing user/kernel pointer.
bpfptr_add() advances the user/kernel pointer.

Signed-off-by: Alexei Starovoitov <ast@kernel.org>
---
 include/linux/bpfptr.h | 81 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 81 insertions(+)
 create mode 100644 include/linux/bpfptr.h

diff --git a/include/linux/bpfptr.h b/include/linux/bpfptr.h
new file mode 100644
index 000000000000..e370acb04977
--- /dev/null
+++ b/include/linux/bpfptr.h
@@ -0,0 +1,81 @@
+/* SPDX-License-Identifier: GPL-2.0-only */
+/* A pointer that can point to either kernel or userspace memory. */
+#ifndef _LINUX_BPFPTR_H
+#define _LINUX_BPFPTR_H
+
+#include <linux/sockptr.h>
+
+typedef sockptr_t bpfptr_t;
+
+static inline bool bpfptr_is_kernel(bpfptr_t bpfptr)
+{
+	return bpfptr.is_kernel;
+}
+
+static inline bpfptr_t KERNEL_BPFPTR(void *p)
+{
+	return (bpfptr_t) { .kernel = p, .is_kernel = true };
+}
+
+static inline bpfptr_t USER_BPFPTR(void __user *p)
+{
+	return (bpfptr_t) { .user = p };
+}
+
+static inline bpfptr_t make_bpfptr(u64 addr, bool is_kernel)
+{
+	if (is_kernel)
+		return (bpfptr_t) {
+			.kernel = (void*) (uintptr_t) addr,
+			.is_kernel = true,
+		};
+	else
+		return (bpfptr_t) {
+			.user = u64_to_user_ptr(addr),
+			.is_kernel = false,
+		};
+}
+
+static inline bool bpfptr_is_null(bpfptr_t bpfptr)
+{
+	if (bpfptr_is_kernel(bpfptr))
+		return !bpfptr.kernel;
+	return !bpfptr.user;
+}
+
+static inline void bpfptr_add(bpfptr_t *bpfptr, size_t val)
+{
+	if (bpfptr_is_kernel(*bpfptr))
+		bpfptr->kernel += val;
+	else
+		bpfptr->user += val;
+}
+
+static inline int copy_from_bpfptr_offset(void *dst, bpfptr_t src,
+					  size_t offset, size_t size)
+{
+	return copy_from_sockptr_offset(dst, (sockptr_t) src, offset, size);
+}
+
+static inline int copy_from_bpfptr(void *dst, bpfptr_t src, size_t size)
+{
+	return copy_from_bpfptr_offset(dst, src, 0, size);
+}
+
+static inline int copy_to_bpfptr_offset(bpfptr_t dst, size_t offset,
+					const void *src, size_t size)
+{
+	return copy_to_sockptr_offset((sockptr_t) dst, offset, src, size);
+}
+
+static inline void *memdup_bpfptr(bpfptr_t src, size_t len)
+{
+	return memdup_sockptr((sockptr_t) src, len);
+}
+
+static inline long strncpy_from_bpfptr(char *dst, bpfptr_t src, size_t count)
+{
+	return strncpy_from_sockptr(dst, (sockptr_t) src, count);
+}
+
+#endif /* _LINUX_BPFPTR_H */
-- 
2.30.2


  parent reply	other threads:[~2021-05-06  3:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  3:44 [PATCH v3 bpf-next 00/17] bpf: syscall program, FD array, loader program, light skeleton Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 01/17] bpf: Introduce bpf_sys_bpf() helper and program type Alexei Starovoitov
2021-05-06  3:44 ` Alexei Starovoitov [this message]
2021-05-06  3:44 ` [PATCH v3 bpf-next 03/17] bpf: Prepare bpf syscall to be used from kernel and user space Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 04/17] libbpf: Support for syscall program type Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 05/17] selftests/bpf: Test " Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 06/17] bpf: Make btf_load command to be bpfptr_t compatible Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 07/17] selftests/bpf: Test for btf_load command Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 08/17] bpf: Introduce fd_idx Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 09/17] libbpf: Support for fd_idx Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 10/17] bpf: Add bpf_btf_find_by_name_kind() helper Alexei Starovoitov
2021-05-06  3:44 ` [PATCH v3 bpf-next 11/17] bpf: Add bpf_sys_close() helper Alexei Starovoitov
2021-05-06  3:45 ` [PATCH v3 bpf-next 12/17] libbpf: Change the order of data and text relocations Alexei Starovoitov
2021-05-06  3:45 ` [PATCH v3 bpf-next 13/17] libbpf: Add bpf_object pointer to kernel_supports() Alexei Starovoitov
2021-05-06  3:45 ` [PATCH v3 bpf-next 14/17] libbpf: Generate loader program out of BPF ELF file Alexei Starovoitov
2021-05-06  3:45 ` [PATCH v3 bpf-next 15/17] libbpf: Use fd_array only with gen_loader Alexei Starovoitov
2021-05-06  3:45 ` [PATCH v3 bpf-next 16/17] bpftool: Use syscall/loader program in "prog load" and "gen skeleton" command Alexei Starovoitov
2021-05-06  3:45 ` [PATCH v3 bpf-next 17/17] selftests/bpf: Convert few tests to light skeleton Alexei Starovoitov

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=20210506034505.25979-3-alexei.starovoitov@gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@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;
as well as URLs for NNTP newsgroup(s).