From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: bpf@vger.kernel.org
Cc: "Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
netdev@vger.kernel.org
Subject: [PATCH bpf-next v2 06/10] bpf: Bump MAX_BPF_STACK size to 768 bytes
Date: Tue, 14 Sep 2021 18:07:45 +0530 [thread overview]
Message-ID: <20210914123750.460750-7-memxor@gmail.com> (raw)
In-Reply-To: <20210914123750.460750-1-memxor@gmail.com>
Increase the maximum stack size accessible to BPF program to 768 bytes.
This is done so that gen_loader can use 94 additional fds for kfunc BTFs
that it passes in to fd_array from the remaining space available for the
loader_stack struct to expand.
Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
---
include/linux/filter.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/filter.h b/include/linux/filter.h
index 4a93c12543ee..b214189ece62 100644
--- a/include/linux/filter.h
+++ b/include/linux/filter.h
@@ -82,8 +82,8 @@ struct ctl_table_header;
*/
#define BPF_SYM_ELF_TYPE 't'
-/* BPF program can access up to 512 bytes of stack space. */
-#define MAX_BPF_STACK 512
+/* BPF program can access up to 768 bytes of stack space. */
+#define MAX_BPF_STACK 768
/* Helper macros for filter block array initializers. */
--
2.33.0
next prev parent reply other threads:[~2021-09-14 12:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 12:37 [PATCH bpf-next v2 00/10] Support kernel module function calls from eBPF Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 01/10] bpf: Introduce BPF support for kernel module function calls Kumar Kartikeya Dwivedi
2021-09-14 19:31 ` kernel test robot
2021-09-14 19:31 ` kernel test robot
2021-09-14 22:01 ` kernel test robot
2021-09-14 22:01 ` kernel test robot
2021-09-14 12:37 ` [PATCH bpf-next v2 02/10] bpf: Be conservative while processing invalid kfunc calls Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 03/10] bpf: btf: Introduce helpers for dynamic BTF set registration Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 04/10] tools: Allow specifying base BTF file in resolve_btfids Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 05/10] bpf: Enable TCP congestion control kfunc from modules Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` Kumar Kartikeya Dwivedi [this message]
2021-09-14 12:37 ` [PATCH bpf-next v2 07/10] libbpf: Support kernel module function calls Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 08/10] libbpf: Resolve invalid weak kfunc calls with imm = 0, off = 0 Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 09/10] libbpf: Update gen_loader to emit BTF_KIND_FUNC relocations Kumar Kartikeya Dwivedi
2021-09-14 12:37 ` [PATCH bpf-next v2 10/10] bpf, selftests: Add basic test for module kfunc call Kumar Kartikeya Dwivedi
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=20210914123750.460750-7-memxor@gmail.com \
--to=memxor@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=toke@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.