Skip to content

Commit b6f467d

Browse files
suchit07-gitKernel Patches Daemon
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]>
1 parent 6978e3e commit b6f467d

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
@@ -4504,7 +4504,7 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx, int subseq_idx,
45044504
* . if (scalar cond K|scalar)
45054505
* . helper_call(.., scalar, ...) where ARG_CONST is expected
45064506
* backtrack through the verifier states and mark all registers and
4507-
* stack slots with spilled constants that these scalar regisers
4507+
* stack slots with spilled constants that these scalar registers
45084508
* should be precise.
45094509
* . during state pruning two registers (or spilled stack slots)
45104510
* are equivalent if both are not precise.
@@ -18436,7 +18436,7 @@ static void clean_verifier_state(struct bpf_verifier_env *env,
1843618436
/* the parentage chains form a tree.
1843718437
* the verifier states are added to state lists at given insn and
1843818438
* pushed into state stack for future exploration.
18439-
* when the verifier reaches bpf_exit insn some of the verifer states
18439+
* when the verifier reaches bpf_exit insn some of the verifier states
1844018440
* stored in the state lists have their final liveness state already,
1844118441
* but a lot of states will get revised from liveness point of view when
1844218442
* the verifier explores other branches.
@@ -19152,7 +19152,7 @@ static bool is_iter_next_insn(struct bpf_verifier_env *env, int insn_idx)
1915219152
* terminology) calls specially: as opposed to bounded BPF loops, it *expects*
1915319153
* states to match, which otherwise would look like an infinite loop. So while
1915419154
* iter_next() calls are taken care of, we still need to be careful and
19155-
* prevent erroneous and too eager declaration of "ininite loop", when
19155+
* prevent erroneous and too eager declaration of "infinite loop", when
1915619156
* iterators are involved.
1915719157
*
1915819158
* Here's a situation in pseudo-BPF assembly form:
@@ -19194,7 +19194,7 @@ static bool is_iter_next_insn(struct bpf_verifier_env *env, int insn_idx)
1919419194
*
1919519195
* This approach allows to keep infinite loop heuristic even in the face of
1919619196
* active iterator. E.g., C snippet below is and will be detected as
19197-
* inifintely looping:
19197+
* infinitely looping:
1919819198
*
1919919199
* struct bpf_iter_num it;
1920019200
* int *p, x;
@@ -24435,7 +24435,7 @@ static int compute_scc(struct bpf_verifier_env *env)
2443524435
* if pre[i] == 0:
2443624436
* recur(i)
2443724437
*
24438-
* Below implementation replaces explicit recusion with array 'dfs'.
24438+
* Below implementation replaces explicit recursion with array 'dfs'.
2443924439
*/
2444024440
for (i = 0; i < insn_cnt; i++) {
2444124441
if (pre[i])

0 commit comments

Comments
 (0)