From: kernel test robot <lkp@intel.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>
Subject: kernel/bpf/liveness.c:1273 arg_track_log() warn: inconsistent indenting
Date: Tue, 23 Jun 2026 01:02:11 +0800 [thread overview]
Message-ID: <202606230027.3jJdEt4k-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ef0c9f75a19532d7675384708fc8621e10850104
commit: bf0c571f7feb6fa05a512e2a5e50702501849d61 bpf: introduce forward arg-tracking dataflow analysis
date: 2 months ago
config: um-randconfig-r072-20260622 (https://download.01.org/0day-ci/archive/20260623/202606230027.3jJdEt4k-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9185-gbcc58b9c
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Fixes: bf0c571f7feb ("bpf: introduce forward arg-tracking dataflow analysis")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606230027.3jJdEt4k-lkp@intel.com/
smatch warnings:
kernel/bpf/liveness.c:1273 arg_track_log() warn: inconsistent indenting
vim +1273 kernel/bpf/liveness.c
1253
1254 static void arg_track_log(struct bpf_verifier_env *env, struct bpf_insn *insn, int idx,
1255 struct arg_track *at_in, struct arg_track *at_stack_in,
1256 struct arg_track *at_out, struct arg_track *at_stack_out)
1257 {
1258 bool printed = false;
1259 int i;
1260
1261 if (!(env->log.level & BPF_LOG_LEVEL2))
1262 return;
1263 for (i = 0; i < MAX_BPF_REG; i++) {
1264 if (arg_track_eq(&at_out[i], &at_in[i]))
1265 continue;
1266 if (!printed) {
1267 verbose(env, "%3d: ", idx);
1268 bpf_verbose_insn(env, insn);
1269 bpf_vlog_reset(&env->log, env->log.end_pos - 1);
1270 printed = true;
1271 }
1272 verbose(env, "\tr%d: ", i); verbose_arg_track(env, &at_in[i]);
> 1273 verbose(env, " -> "); verbose_arg_track(env, &at_out[i]);
1274 }
1275 for (i = 0; i < MAX_ARG_SPILL_SLOTS; i++) {
1276 if (arg_track_eq(&at_stack_out[i], &at_stack_in[i]))
1277 continue;
1278 if (!printed) {
1279 verbose(env, "%3d: ", idx);
1280 bpf_verbose_insn(env, insn);
1281 bpf_vlog_reset(&env->log, env->log.end_pos - 1);
1282 printed = true;
1283 }
1284 verbose(env, "\tfp%+d: ", -(i + 1) * 8); verbose_arg_track(env, &at_stack_in[i]);
1285 verbose(env, " -> "); verbose_arg_track(env, &at_stack_out[i]);
1286 }
1287 if (printed)
1288 verbose(env, "\n");
1289 }
1290
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-22 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202606230027.3jJdEt4k-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=eddyz87@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®