Skip to content

Commit 89ee838

Browse files
Dave ThalerAlexei Starovoitov
authored andcommitted
bpf, docs: specify which BPF_ABS and BPF_IND fields were zero
Specifying which fields were unused allows IANA to only list as deprecated instructions that were actually used, leaving the rest as unassigned and possibly available for future use for something else. Signed-off-by: Dave Thaler <dthaler1968@gmail.com> Acked-by: David Vernet <void@manifault.com> Link: https://lore.kernel.org/r/20240221175419.16843-1-dthaler1968@gmail.com Signed-off-by: Alexei Starovoitov <ast@kernel.org>
1 parent c1bb68f commit 89ee838

1 file changed

Lines changed: 4 additions & 3 deletions

File tree

Documentation/bpf/standardization/instruction-set.rst

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -658,6 +658,7 @@ Legacy BPF Packet access instructions
658658
BPF previously introduced special instructions for access to packet data that were
659659
carried over from classic BPF. These instructions used an instruction
660660
class of BPF_LD, a size modifier of BPF_W, BPF_H, or BPF_B, and a
661-
mode modifier of BPF_ABS or BPF_IND. However, these instructions are
662-
deprecated and should no longer be used. All legacy packet access
663-
instructions belong to the "legacy" conformance group.
661+
mode modifier of BPF_ABS or BPF_IND. The 'dst_reg' and 'offset' fields were
662+
set to zero, and 'src_reg' was set to zero for BPF_ABS. However, these
663+
instructions are deprecated and should no longer be used. All legacy packet
664+
access instructions belong to the "legacy" conformance group.

0 commit comments

Comments
 (0)