@@ -43,12 +43,12 @@ internal compiler that generates a structure that can eventually be loaded
via SO_ATTACH_FILTER to the kernel. ``tcpdump -i em1 port 22 -ddd``
displays what is being placed into this structure.
-Although we were only speaking about sockets here, BPF in Linux is used
-in many more places. There's xt_bpf for netfilter, cls_bpf in the kernel
-qdisc layer, SECCOMP-BPF (SECure COMPuting [1]), and lots of other places
-such as team driver, PTP code, etc where BPF is being used.
-
- [1] Documentation/userspace-api/seccomp_filter.rst
+Although we were only speaking about sockets here, BPF in Linux is used in
+many more places. There's xt_bpf for netfilter, cls_bpf in the kernel qdisc
+layer, SECCOMP-BPF (SECure COMPuting
+:ref:`Documentation/userspace-api/seccomp_filter.rst <seccomp_filter>`),
+and lots of other places such as team driver, PTP code, etc where BPF is
+being used.
Original BPF paper:
@@ -2,6 +2,8 @@
Seccomp BPF (SECure COMPuting with filters)
===========================================
+.. _seccomp_filter:
+
Introduction
============
Typical RST documents embed the reference link straight in the text. Currently document uses a '[1]' with the reference below that paragraph. Use RST :ref:`path/to/file` <label>` format and embed the reference to seccomp_filter directly in the text. Add a label to seccomp_filter.rst to enable the reference to function correctly. Signed-off-by: Tobin C. Harding <me@tobin.cc> --- Documentation/networking/filter.rst | 12 ++++++------ Documentation/userspace-api/seccomp_filter.rst | 2 ++ 2 files changed, 8 insertions(+), 6 deletions(-)