diff options
author | David S. Miller <davem@davemloft.net> | 2019-03-29 21:00:28 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-03-29 21:00:28 -0700 |
commit | 22bdf7d459ceff6eb06a99364b1d75ecb2fcafe5 (patch) | |
tree | 73907c9d5beb903e103ed2af11f3a050e02e82d4 /Documentation | |
parent | 19c847444d1e94ca1f6183a3eea968d00d5d0a95 (diff) | |
parent | 676e4a6fe703f2dae699ee9d56f14516f9ada4ea (diff) | |
download | linux-22bdf7d459ceff6eb06a99364b1d75ecb2fcafe5.tar.gz linux-22bdf7d459ceff6eb06a99364b1d75ecb2fcafe5.tar.bz2 linux-22bdf7d459ceff6eb06a99364b1d75ecb2fcafe5.zip |
Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf
Daniel Borkmann says:
====================
pull-request: bpf 2019-03-29
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Bug fix in BTF deduplication that was mishandling an equivalence
comparison, from Andrii.
2) libbpf Makefile fixes to properly link against libelf for the shared
object and to actually export AF_XDP's xsk.h header, from Björn.
3) Fix use after free in bpf inode eviction, from Daniel.
4) Fix a bug in skb creation out of cpumap redirect, from Jesper.
5) Remove an unnecessary and triggerable WARN_ONCE() in max number
of call stack frames checking in verifier, from Paul.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/bpf/btf.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/bpf/btf.rst b/Documentation/bpf/btf.rst index 9a60a5d60e38..7313d354f20e 100644 --- a/Documentation/bpf/btf.rst +++ b/Documentation/bpf/btf.rst @@ -148,16 +148,16 @@ The ``btf_type.size * 8`` must be equal to or greater than ``BTF_INT_BITS()`` for the type. The maximum value of ``BTF_INT_BITS()`` is 128. The ``BTF_INT_OFFSET()`` specifies the starting bit offset to calculate values -for this int. For example, a bitfield struct member has: * btf member bit -offset 100 from the start of the structure, * btf member pointing to an int -type, * the int type has ``BTF_INT_OFFSET() = 2`` and ``BTF_INT_BITS() = 4`` +for this int. For example, a bitfield struct member has: + * btf member bit offset 100 from the start of the structure, + * btf member pointing to an int type, + * the int type has ``BTF_INT_OFFSET() = 2`` and ``BTF_INT_BITS() = 4`` Then in the struct memory layout, this member will occupy ``4`` bits starting from bits ``100 + 2 = 102``. Alternatively, the bitfield struct member can be the following to access the same bits as the above: - * btf member bit offset 102, * btf member pointing to an int type, * the int type has ``BTF_INT_OFFSET() = 0`` and ``BTF_INT_BITS() = 4`` |