Skip to content

Commit d556ea6

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 f34ad0b commit d556ea6

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
@@ -4518,7 +4518,7 @@ static int backtrack_insn(struct bpf_verifier_env *env, int idx, int subseq_idx,
45184518
* . if (scalar cond K|scalar)
45194519
* . helper_call(.., scalar, ...) where ARG_CONST is expected
45204520
* backtrack through the verifier states and mark all registers and
4521-
* stack slots with spilled constants that these scalar regisers
4521+
* stack slots with spilled constants that these scalar registers
45224522
* should be precise.
45234523
* . during state pruning two registers (or spilled stack slots)
45244524
* are equivalent if both are not precise.
@@ -18450,7 +18450,7 @@ static void clean_verifier_state(struct bpf_verifier_env *env,
1845018450
/* the parentage chains form a tree.
1845118451
* the verifier states are added to state lists at given insn and
1845218452
* pushed into state stack for future exploration.
18453-
* when the verifier reaches bpf_exit insn some of the verifer states
18453+
* when the verifier reaches bpf_exit insn some of the verifier states
1845418454
* stored in the state lists have their final liveness state already,
1845518455
* but a lot of states will get revised from liveness point of view when
1845618456
* the verifier explores other branches.
@@ -19166,7 +19166,7 @@ static bool is_iter_next_insn(struct bpf_verifier_env *env, int insn_idx)
1916619166
* terminology) calls specially: as opposed to bounded BPF loops, it *expects*
1916719167
* states to match, which otherwise would look like an infinite loop. So while
1916819168
* iter_next() calls are taken care of, we still need to be careful and
19169-
* prevent erroneous and too eager declaration of "ininite loop", when
19169+
* prevent erroneous and too eager declaration of "infinite loop", when
1917019170
* iterators are involved.
1917119171
*
1917219172
* Here's a situation in pseudo-BPF assembly form:
@@ -19208,7 +19208,7 @@ static bool is_iter_next_insn(struct bpf_verifier_env *env, int insn_idx)
1920819208
*
1920919209
* This approach allows to keep infinite loop heuristic even in the face of
1921019210
* active iterator. E.g., C snippet below is and will be detected as
19211-
* inifintely looping:
19211+
* infinitely looping:
1921219212
*
1921319213
* struct bpf_iter_num it;
1921419214
* int *p, x;
@@ -24449,7 +24449,7 @@ static int compute_scc(struct bpf_verifier_env *env)
2444924449
* if pre[i] == 0:
2445024450
* recur(i)
2445124451
*
24452-
* Below implementation replaces explicit recusion with array 'dfs'.
24452+
* Below implementation replaces explicit recursion with array 'dfs'.
2445324453
*/
2445424454
for (i = 0; i < insn_cnt; i++) {
2445524455
if (pre[i])

0 commit comments

Comments
 (0)