diff options
| author | Shahab Vahedi <[email protected]> | 2022-06-24 14:14:11 +0000 |
|---|---|---|
| committer | Andrii Nakryiko <[email protected]> | 2022-06-24 13:58:32 -0700 |
| commit | 2f6d1e0f8ff3cf66b1eef8ed36f6c64d2e679284 (patch) | |
| tree | 63e2e7ffc5ea9d97ba85fbe3c6ff8b078bab7683 | |
| parent | 780d3d5a24bbdd48cb43f35afb6f5b7544cdf45a (diff) | |
bpf, docs: Fix the code formatting in instruction-set
A minor typo fix to include "| BPF_LD" into its previous
code phrase:
``BPF_IND`` | BPF_LD --> ``BPF_IND | BPF_LD``
Signed-off-by: Shahab Vahedi <[email protected]>
Signed-off-by: Andrii Nakryiko <[email protected]>
Link: https://lore.kernel.org/bpf/[email protected]
| -rw-r--r-- | Documentation/bpf/instruction-set.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/bpf/instruction-set.rst b/Documentation/bpf/instruction-set.rst index 9e27fbdb2206..1b0e6711dec9 100644 --- a/Documentation/bpf/instruction-set.rst +++ b/Documentation/bpf/instruction-set.rst @@ -351,7 +351,7 @@ These instructions have seven implicit operands: * Register R0 is an implicit output which contains the data fetched from the packet. * Registers R1-R5 are scratch registers that are clobbered after a call to - ``BPF_ABS | BPF_LD`` or ``BPF_IND`` | BPF_LD instructions. + ``BPF_ABS | BPF_LD`` or ``BPF_IND | BPF_LD`` instructions. These instructions have an implicit program exit condition as well. When an eBPF program is trying to access the data beyond the packet boundary, the |