On Fri, Jun 21, 2019 at 1:36 AM kernel test robot <rong.a.chen@xxxxxxxxx> wrote: > # #340/p direct packet access: test22 (x += pkt_ptr, 3) OK > # #341/p direct packet access: test23 (x += pkt_ptr, 4) FAIL > # Unexpected success to load! > # verification time 17 usec > # stack depth 8 > # processed 18 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0 > # #342/p direct packet access: test24 (x += pkt_ptr, 5) OK > # #343/p direct packet access: test25 (marking on <, good access) OK .. > # #673/p meta access, test9 OK > # #674/p meta access, test10 FAIL > # Unexpected success to load! > # verification time 29 usec > # stack depth 8 > # processed 19 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0 > # #675/p meta access, test11 OK Hi Rong, the patch quoted is not in bpf-next/net-next. This patch is work-in-progress that I posted to mailing list and pushed into my own git branch on kernel.org. It's awesome that build bot does this early testing. I really like it. Would be great if the bot can add a tag to email subject that it's testing this not yet merged patch. Right now since the email says commit: 6c409a3aee945e50c6dd4109689f52 it felt that this is real commit and my initial reaction was that 'ohh something is broken in the merge code' which wasn't the case :)
