From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 5/5] bpf: Check truncation on 32bit div/mod by zero
Date: Fri, 30 Apr 2021 10:46:49 +0200 [thread overview]
Message-ID: <YIvD+cd3I4ExCIY7@yuki> (raw)
In-Reply-To: <20210429150510.21585-6-rpalethorpe@suse.com>
Hi!
> +static int load_prog(void)
> +{
> + struct bpf_insn_buf prog_insn = { 0 };
> + /* r6 = 1 << 32
> + * r7 = -1
> + */
> + const struct bpf_insn set_src_dst_insn[] = {
> + BPF_LD_IMM64(BPF_REG_6, 1ULL << 32),
> + BPF_MOV64_IMM(BPF_REG_7, -1LL),
> + };
> + /* w7 /= w6 */
> + const struct bpf_insn div_insn =
> + BPF_ALU32_REG(BPF_DIV, BPF_REG_7, BPF_REG_6);
> + /* w7 %= w6 */
> + const struct bpf_insn mod_insn =
> + BPF_ALU32_REG(BPF_MOD, BPF_REG_7, BPF_REG_6);
> + /* exit(0) */
> + const struct bpf_insn exit_insn[] = {
> + BPF_MOV64_IMM(BPF_REG_0, 0),
> + BPF_EXIT_INSN()
> + };
> +
> + bpf_insn_buf_cat(&prog_insn, set_src_dst_insn, sizeof(set_src_dst_insn));
> + bpf_insn_buf_cat(&prog_insn, &div_insn, sizeof(div_insn));
> +
> + bpf_insn_buf_array_set(&prog_insn, map_fd, 0, BPF_REG_6);
> + bpf_insn_buf_array_set(&prog_insn, map_fd, 1, BPF_REG_7);
> +
> + bpf_insn_buf_cat(&prog_insn, set_src_dst_insn, sizeof(set_src_dst_insn));
> + bpf_insn_buf_cat(&prog_insn, &mod_insn, sizeof(mod_insn));
> +
> + bpf_insn_buf_array_set(&prog_insn, map_fd, 2, BPF_REG_6);
> + bpf_insn_buf_array_set(&prog_insn, map_fd, 3, BPF_REG_7);
> +
> + bpf_insn_buf_cat(&prog_insn, exit_insn, sizeof(exit_insn));
> +
> + bpf_init_prog_attr(attr, prog_insn.insn, prog_insn.byte_len, log, BUFSIZE);
I find this completely unreadable to be honest, the array with
instructions is much better.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2021-04-30 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 15:05 [LTP] [PATCH v2 0/5] BPF refactor and add bpf_prog05 Richard Palethorpe
2021-04-29 15:05 ` [LTP] [PATCH v2 1/5] lapi/bpf: Add /=, %= and BPF_MAXINSNS Richard Palethorpe
2021-04-29 15:05 ` [LTP] [PATCH v2 2/5] bpf: Add map_array helper functions Richard Palethorpe
2021-04-30 8:31 ` Cyril Hrubis
2021-05-05 10:27 ` Richard Palethorpe
2021-04-29 15:05 ` [LTP] [PATCH v2 3/5] bpf: Add helper to run socket programs Richard Palethorpe
2021-04-30 8:38 ` Cyril Hrubis
2021-04-29 15:05 ` [LTP] [PATCH v2 4/5] bpf: Add bpf_insn_buf, map and instruction concatenation helpers Richard Palethorpe
2021-04-30 8:44 ` Cyril Hrubis
2021-04-29 15:05 ` [LTP] [PATCH v2 5/5] bpf: Check truncation on 32bit div/mod by zero Richard Palethorpe
2021-04-30 8:46 ` Cyril Hrubis [this message]
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=YIvD+cd3I4ExCIY7@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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