Skip to content

Commit 5b4c54a

Browse files
suchit07-gitAlexei Starovoitov
authored andcommitted
bpf: Fix various typos in verifier.c comments
This patch fixes several minor typos in comments within the BPF verifier. No changes in functionality. Signed-off-by: Suchit Karunakaran <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alexei Starovoitov <[email protected]>
1 parent a9f8d8a commit 5b4c54a

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

kernel/bpf/verifier.c

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4557,7 +4557,7 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx, int subseq_idx,
45574557
* . if (scalar cond K|scalar)
45584558
* . helper_call(.., scalar, ...) where ARG_CONST is expected
45594559
* backtrack through the verifier states and mark all registers and
4560-
* stack slots with spilled constants that these scalar regisers
4560+
* stack slots with spilled constants that these scalar registers
45614561
* should be precise.
45624562
* . during state pruning two registers (or spilled stack slots)
45634563
* are equivalent if both are not precise.
@@ -18489,7 +18489,7 @@ static void clean_verifier_state(struct bpf_verifier_env *env,
1848918489
/* the parentage chains form a tree.
1849018490
* the verifier states are added to state lists at given insn and
1849118491
* pushed into state stack for future exploration.
18492-
* when the verifier reaches bpf_exit insn some of the verifer states
18492+
* when the verifier reaches bpf_exit insn some of the verifier states
1849318493
* stored in the state lists have their final liveness state already,
1849418494
* but a lot of states will get revised from liveness point of view when
1849518495
* the verifier explores other branches.
@@ -19205,7 +19205,7 @@ static bool is_iter_next_insn(struct bpf_verifier_env *env, int insn_idx)
1920519205
* terminology) calls specially: as opposed to bounded BPF loops, it *expects*
1920619206
* states to match, which otherwise would look like an infinite loop. So while
1920719207
* iter_next() calls are taken care of, we still need to be careful and
19208-
* prevent erroneous and too eager declaration of "ininite loop", when
19208+
* prevent erroneous and too eager declaration of "infinite loop", when
1920919209
* iterators are involved.
1921019210
*
1921119211
* Here's a situation in pseudo-BPF assembly form:
@@ -19247,7 +19247,7 @@ static bool is_iter_next_insn(struct bpf_verifier_env *env, int insn_idx)
1924719247
*
1924819248
* This approach allows to keep infinite loop heuristic even in the face of
1924919249
* active iterator. E.g., C snippet below is and will be detected as
19250-
* inifintely looping:
19250+
* infinitely looping:
1925119251
*
1925219252
* struct bpf_iter_num it;
1925319253
* int *p, x;
@@ -24488,7 +24488,7 @@ static int compute_scc(struct bpf_verifier_env *env)
2448824488
* if pre[i] == 0:
2448924489
* recur(i)
2449024490
*
24491-
* Below implementation replaces explicit recusion with array 'dfs'.
24491+
* Below implementation replaces explicit recursion with array 'dfs'.
2449224492
*/
2449324493
for (i = 0; i < insn_cnt; i++) {
2449424494
if (pre[i])

0 commit comments

Comments
 (0)