Commit 41d0c467 authored by Yusheng Zheng's avatar Yusheng Zheng Committed by Andrii Nakryiko
Browse files

libbpf: Fix some typos in comments 



Fix some spelling errors in the code comments of libbpf:

betwen -> between
paremeters -> parameters
knowning -> knowing
definiton -> definition
compatiblity -> compatibility
overriden -> overridden
occured -> occurred
proccess -> process
managment -> management
nessary -> necessary

Signed-off-by: default avatarYusheng Zheng <yunwei356@gmail.com>
Signed-off-by: default avatarAndrii Nakryiko <andrii@kernel.org>
Link: https://lore.kernel.org/bpf/20240909225952.30324-1-yunwei356@gmail.com
parent 72d8508e

tools/lib/bpf/bpf_helpers.h

+1 −1
Original line number Diff line number Diff line
@@ -341,7 +341,7 @@ extern void bpf_iter_num_destroy(struct bpf_iter_num *it) __weak __ksym; 
 * I.e., it looks almost like high-level for each loop in other languages,

 * supports continue/break, and is verifiable by BPF verifier.

 *

 * For iterating integers, the difference betwen bpf_for_each(num, i, N, M)

 * For iterating integers, the difference between bpf_for_each(num, i, N, M)

 * and bpf_for(i, N, M) is in that bpf_for() provides additional proof to

 * verifier that i is in [N, M) range, and in bpf_for_each() case i is `int

 * *`, not just `int`. So for integers bpf_for() is more convenient.

tools/lib/bpf/bpf_tracing.h

+1 −1
Original line number Diff line number Diff line
@@ -808,7 +808,7 @@ struct pt_regs; 
 * tp_btf/fentry/fexit BPF programs. It hides the underlying platform-specific

 * low-level way of getting kprobe input arguments from struct pt_regs, and

 * provides a familiar typed and named function arguments syntax and

 * semantics of accessing kprobe input paremeters.

 * semantics of accessing kprobe input parameters.

 *

 * Original struct pt_regs* context is preserved as 'ctx' argument. This might

 * be necessary when using BPF helpers like bpf_perf_event_output().

tools/lib/bpf/btf.c

+1 −1
Original line number Diff line number Diff line
@@ -4230,7 +4230,7 @@ static bool btf_dedup_identical_structs(struct btf_dedup *d, __u32 id1, __u32 id 
 * consists of portions of the graph that come from multiple compilation units.

 * This is due to the fact that types within single compilation unit are always

 * deduplicated and FWDs are already resolved, if referenced struct/union

 * definiton is available. So, if we had unresolved FWD and found corresponding

 * definition is available. So, if we had unresolved FWD and found corresponding

 * STRUCT/UNION, they will be from different compilation units. This

 * consequently means that when we "link" FWD to corresponding STRUCT/UNION,

 * type graph will likely have at least two different BTF types that describe

tools/lib/bpf/btf.h

+1 −1
Original line number Diff line number Diff line
@@ -286,7 +286,7 @@ LIBBPF_API void btf_dump__free(struct btf_dump *d); 
LIBBPF_API int btf_dump__dump_type(struct btf_dump *d, __u32 id);



struct btf_dump_emit_type_decl_opts {

	/* size of this struct, for forward/backward compatiblity */

	/* size of this struct, for forward/backward compatibility */

	size_t sz;

	/* optional field name for type declaration, e.g.:

	 * - struct my_struct <FNAME>

tools/lib/bpf/btf_dump.c

+1 −1
Original line number Diff line number Diff line
@@ -304,7 +304,7 @@ int btf_dump__dump_type(struct btf_dump *d, __u32 id) 
 * definition, in which case they have to be declared inline as part of field

 * type declaration; or as a top-level anonymous enum, typically used for

 * declaring global constants. It's impossible to distinguish between two

 * without knowning whether given enum type was referenced from other type:

 * without knowing whether given enum type was referenced from other type:

 * top-level anonymous enum won't be referenced by anything, while embedded

 * one will.

 */