From: Dan Carpenter <dan.carpenter@linaro.org>
To: imagedong@tencent.com
Cc: bpf@vger.kernel.org
Subject: [bug report] bpf, x86: allow function arguments up to 12 for TRACING
Date: Mon, 17 Jul 2023 17:48:53 +0300 [thread overview]
Message-ID: <09784025-a812-493f-9829-5e26c8691e07@moroto.mountain> (raw)
Hello Menglong Dong,
The patch 473e3150e30a: "bpf, x86: allow function arguments up to 12
for TRACING" from Jul 13, 2023 (linux-next), leads to the following
Smatch static checker warning:
arch/x86/net/bpf_jit_comp.c:1999 save_args()
error: uninitialized symbol 'first_off'.
arch/x86/net/bpf_jit_comp.c
1925 static void save_args(const struct btf_func_model *m, u8 **prog,
1926 int stack_size, bool for_call_origin)
1927 {
1928 int arg_regs, first_off, nr_regs = 0, nr_stack_slots = 0;
1929 int i, j;
1930
1931 /* Store function arguments to stack.
1932 * For a function that accepts two pointers the sequence will be:
1933 * mov QWORD PTR [rbp-0x10],rdi
1934 * mov QWORD PTR [rbp-0x8],rsi
1935 */
1936 for (i = 0; i < min_t(int, m->nr_args, MAX_BPF_FUNC_ARGS); i++) {
1937 arg_regs = (m->arg_size[i] + 7) / 8;
1938
1939 /* According to the research of Yonghong, struct members
1940 * should be all in register or all on the stack.
1941 * Meanwhile, the compiler will pass the argument on regs
1942 * if the remaining regs can hold the argument.
1943 *
1944 * Disorder of the args can happen. For example:
1945 *
1946 * struct foo_struct {
1947 * long a;
1948 * int b;
1949 * };
1950 * int foo(char, char, char, char, char, struct foo_struct,
1951 * char);
1952 *
1953 * the arg1-5,arg7 will be passed by regs, and arg6 will
1954 * by stack.
1955 */
1956 if (nr_regs + arg_regs > 6) {
first_off is not set on else path. It's also in a loop so maybe there
is some guarantee that we will hit an else path...
1957 /* copy function arguments from origin stack frame
1958 * into current stack frame.
1959 *
1960 * The starting address of the arguments on-stack
1961 * is:
1962 * rbp + 8(push rbp) +
1963 * 8(return addr of origin call) +
1964 * 8(return addr of the caller)
1965 * which means: rbp + 24
1966 */
1967 for (j = 0; j < arg_regs; j++) {
1968 emit_ldx(prog, BPF_DW, BPF_REG_0, BPF_REG_FP,
1969 nr_stack_slots * 8 + 0x18);
1970 emit_stx(prog, BPF_DW, BPF_REG_FP, BPF_REG_0,
1971 -stack_size);
1972
1973 if (!nr_stack_slots)
1974 first_off = stack_size;
1975 stack_size -= 8;
1976 nr_stack_slots++;
1977 }
1978 } else {
1979 /* Only copy the arguments on-stack to current
1980 * 'stack_size' and ignore the regs, used to
1981 * prepare the arguments on-stack for orign call.
1982 */
1983 if (for_call_origin) {
1984 nr_regs += arg_regs;
1985 continue;
1986 }
1987
1988 /* copy the arguments from regs into stack */
1989 for (j = 0; j < arg_regs; j++) {
1990 emit_stx(prog, BPF_DW, BPF_REG_FP,
1991 nr_regs == 5 ? X86_REG_R9 : BPF_REG_1 + nr_regs,
1992 -stack_size);
1993 stack_size -= 8;
1994 nr_regs++;
1995 }
1996 }
1997 }
1998
--> 1999 clean_stack_garbage(m, prog, nr_stack_slots, first_off);
2000 }
regards,
dan carpenter
next reply other threads:[~2023-07-17 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 14:48 Dan Carpenter [this message]
2023-07-19 7:58 ` [bug report] bpf, x86: allow function arguments up to 12 for TRACING Menglong Dong
2023-07-19 8:22 ` Dan Carpenter
2023-07-19 8:55 ` Menglong Dong
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=09784025-a812-493f-9829-5e26c8691e07@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=bpf@vger.kernel.org \
--cc=imagedong@tencent.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).