From: kernel test robot <lkp@intel.com>
To: Eduard Zingerman <eddyz87@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH bpf-next v3 4/7] selftests/bpf: tests with delayed read/precision makrs in loop body
Date: Tue, 24 Oct 2023 09:43:19 +0800 [thread overview]
Message-ID: <202310240902.mvutnvcZ-lkp@intel.com> (raw)
In-Reply-To: <20231024000917.12153-5-eddyz87@gmail.com>
Hi Eduard,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Eduard-Zingerman/bpf-move-explored_state-closer-to-the-beginning-of-verifier-c/20231024-081049
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20231024000917.12153-5-eddyz87%40gmail.com
patch subject: [PATCH bpf-next v3 4/7] selftests/bpf: tests with delayed read/precision makrs in loop body
reproduce: (https://download.01.org/0day-ci/archive/20231024/202310240902.mvutnvcZ-lkp@intel.com/reproduce)
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
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202310240902.mvutnvcZ-lkp@intel.com/
# many are suggestions rather than must-fix
WARNING:SPLIT_STRING: quoted string split across lines
#82: FILE: tools/testing/selftests/bpf/progs/iters.c:767:
+ "1:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#91: FILE: tools/testing/selftests/bpf/progs/iters.c:776:
+ "3:"
+ "r1 = r7;"
WARNING:SPLIT_STRING: quoted string split across lines
#97: FILE: tools/testing/selftests/bpf/progs/iters.c:782:
+ "2:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#159: FILE: tools/testing/selftests/bpf/progs/iters.c:844:
+ "1:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#169: FILE: tools/testing/selftests/bpf/progs/iters.c:854:
+ "3:"
+ "r0 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#176: FILE: tools/testing/selftests/bpf/progs/iters.c:861:
+ "2:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#252: FILE: tools/testing/selftests/bpf/progs/iters.c:937:
+ "j_loop_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#264: FILE: tools/testing/selftests/bpf/progs/iters.c:949:
+ "i_loop_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#269: FILE: tools/testing/selftests/bpf/progs/iters.c:954:
+ "check_one_r6_%=:"
+ "if r6 != 1 goto check_zero_r6_%=;"
WARNING:SPLIT_STRING: quoted string split across lines
#274: FILE: tools/testing/selftests/bpf/progs/iters.c:959:
+ "check_zero_r6_%=:"
+ "if r6 != 0 goto i_loop_%=;"
WARNING:SPLIT_STRING: quoted string split across lines
#280: FILE: tools/testing/selftests/bpf/progs/iters.c:965:
+ "check_one_r7_%=:"
+ "if r7 != 1 goto i_loop_%=;"
WARNING:SPLIT_STRING: quoted string split across lines
#294: FILE: tools/testing/selftests/bpf/progs/iters.c:979:
+ "i_loop_end_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#302: FILE: tools/testing/selftests/bpf/progs/iters.c:987:
+ "j_loop_end_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#346: FILE: tools/testing/selftests/bpf/progs/iters.c:1031:
+ "loop_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#359: FILE: tools/testing/selftests/bpf/progs/iters.c:1044:
+ "loop_end_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#400: FILE: tools/testing/selftests/bpf/progs/iters.c:1085:
+ "loop_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#409: FILE: tools/testing/selftests/bpf/progs/iters.c:1094:
+ "loop_end_%=:"
+ "r1 = r10;"
WARNING:REPEATED_WORD: Possible repeated word: 'to'
#454: FILE: tools/testing/selftests/bpf/progs/iters.c:1139:
+ * to to avoid comparing current state with too many explored
WARNING:SPLIT_STRING: quoted string split across lines
#476: FILE: tools/testing/selftests/bpf/progs/iters.c:1161:
+ "loop_%=:"
+ "r1 = r10;"
WARNING:SPLIT_STRING: quoted string split across lines
#537: FILE: tools/testing/selftests/bpf/progs/iters.c:1222:
+ "loop_end_%=:"
+ "r1 = r10;"
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-24 1:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 0:09 [PATCH bpf-next v3 0/7] exact states comparison for iterator convergence checks Eduard Zingerman
2023-10-24 0:09 ` [PATCH bpf-next v3 1/7] bpf: move explored_state() closer to the beginning of verifier.c Eduard Zingerman
2023-10-24 0:09 ` [PATCH bpf-next v3 2/7] bpf: extract same_callsites() as utility function Eduard Zingerman
2023-10-24 0:09 ` [PATCH bpf-next v3 3/7] bpf: exact states comparison for iterator convergence checks Eduard Zingerman
2023-10-24 0:09 ` [PATCH bpf-next v3 4/7] selftests/bpf: tests with delayed read/precision makrs in loop body Eduard Zingerman
2023-10-24 1:43 ` kernel test robot [this message]
2023-10-24 0:09 ` [PATCH bpf-next v3 5/7] bpf: correct loop detection for iterators convergence Eduard Zingerman
2023-10-24 0:09 ` [PATCH bpf-next v3 6/7] selftests/bpf: test if state loops are detected in a tricky case Eduard Zingerman
2023-10-24 0:09 ` [PATCH bpf-next v3 7/7] bpf: print full verifier states on infinite loop detection Eduard Zingerman
2023-10-24 5:10 ` [PATCH bpf-next v3 0/7] exact states comparison for iterator convergence checks patchwork-bot+netdevbpf
2023-10-24 5:58 ` Andrii Nakryiko
2023-10-24 11:57 ` Eduard Zingerman
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=202310240902.mvutnvcZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--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