All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael Passos" <rafael@rcpassos.me>
To: <ast@kernel.org>,<andrii@kernel.org>,<daniel@iogearbox.net>
Cc: "Rafael Passos" <rafael@rcpassos.me>, bpf@vger.kernel.org
Subject: [PATCH bpf-next 2/2] bpf: fix typo in function save_aux_ptr_type
Date: Wed, 17 Apr 2024 15:49:15 -0300	[thread overview]
Message-ID: <faf2d9cf-3326-4932-b735-5dbee87e67cb@smtp-relay.sendinblue.com> (raw)
In-Reply-To: <20240417184918.21472-1-rafael@rcpassos.me>

I found this typo in the save_aux_ptr_type function.
s/allow_trust_missmatch/allow_trust_mismatch/
I did not find this anywhere else in the codebase.

Signed-off-by: Rafael Passos <rafael@rcpassos.me>
---
 kernel/bpf/verifier.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index 537cdccb8363..5a7e34e83a5b 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -6971,7 +6971,7 @@ static int check_mem_access(struct bpf_verifier_env *env, int insn_idx, u32 regn
 }
 
 static int save_aux_ptr_type(struct bpf_verifier_env *env, enum bpf_reg_type type,
-			     bool allow_trust_missmatch);
+			     bool allow_trust_mismatch);
 
 static int check_atomic(struct bpf_verifier_env *env, int insn_idx, struct bpf_insn *insn)
 {
@@ -17530,7 +17530,7 @@ static bool reg_type_mismatch(enum bpf_reg_type src, enum bpf_reg_type prev)
 }
 
 static int save_aux_ptr_type(struct bpf_verifier_env *env, enum bpf_reg_type type,
-			     bool allow_trust_missmatch)
+			     bool allow_trust_mismatch)
 {
 	enum bpf_reg_type *prev_type = &env->insn_aux_data[env->insn_idx].ptr_type;
 
@@ -17548,7 +17548,7 @@ static int save_aux_ptr_type(struct bpf_verifier_env *env, enum bpf_reg_type typ
 		 * src_reg == stack|map in some other branch.
 		 * Reject it.
 		 */
-		if (allow_trust_missmatch &&
+		if (allow_trust_mismatch &&
 		    base_type(type) == PTR_TO_BTF_ID &&
 		    base_type(*prev_type) == PTR_TO_BTF_ID) {
 			/*
-- 
2.44.0



      parent reply	other threads:[~2024-04-17 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240417180446.9300-1-rafael@rcpassos.me>
2024-04-17 17:52 ` [PATCH] bpf: fix typo in function save_aux_ptr_type Rafael Passos
2024-04-22 15:20   ` patchwork-bot+netdevbpf
2024-04-17 18:49 ` [PATCH bpf-next 1/2] bpf: fixes typos in comments Rafael Passos
2024-04-22 16:00   ` patchwork-bot+netdevbpf
     [not found] ` <20240417184918.21472-1-rafael@rcpassos.me>
2024-04-17 18:49   ` Rafael Passos [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=faf2d9cf-3326-4932-b735-5dbee87e67cb@smtp-relay.sendinblue.com \
    --to=rafael@rcpassos.me \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.