From: Martin KaFai Lau <martin.lau@linux.dev>
To: bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@meta.com, kernel test robot <lkp@intel.com>
Subject: [PATCH bpf-next 2/2] bpf: Fix indentation issue in epilogue_idx
Date: Wed, 4 Sep 2024 11:08:45 -0700 [thread overview]
Message-ID: <20240904180847.56947-3-martin.lau@linux.dev> (raw)
In-Reply-To: <20240904180847.56947-1-martin.lau@linux.dev>
From: Martin KaFai Lau <martin.lau@kernel.org>
There is a report on new indentation issue in epilogue_idx.
This patch fixed it.
Fixes: 169c31761c8d ("bpf: Add gen_epilogue to bpf_verifier_ops")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202408311622.4GzlzN33-lkp@intel.com/
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
---
kernel/bpf/verifier.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index 8bfb14d1eb7a..b806afeba212 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -19800,7 +19800,7 @@ static int convert_ctx_accesses(struct bpf_verifier_env *env)
* least one ctx ptr saving insn before the
* epilogue.
*/
- epilogue_idx = i + delta;
+ epilogue_idx = i + delta;
}
goto patch_insn_buf;
} else {
--
2.43.5
next prev parent reply other threads:[~2024-09-04 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 18:08 [PATCH bpf-next 0/2] bpf: Follow up on gen_epilogue Martin KaFai Lau
2024-09-04 18:08 ` [PATCH bpf-next 1/2] bpf: Remove the insn_buf array stack usage from the inline_bpf_loop() Martin KaFai Lau
2024-09-04 18:08 ` Martin KaFai Lau [this message]
2024-09-04 19:06 ` [PATCH bpf-next 0/2] bpf: Follow up on gen_epilogue Eduard Zingerman
2024-09-04 19:50 ` patchwork-bot+netdevbpf
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=20240904180847.56947-3-martin.lau@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=lkp@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox