test_verifier in ubuntu_bpf failed with 3 test cases (#27, #30, #150) on J-AMD64

Bug #1991351 reported by Po-Hsu Lin
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

Different from Jammy 5.15 generic kernel and J-oracle kernel, which has 40 failures reported in this test_verifier test case (bug 1991215). And 6 failures in GKEOP (bug 1991376)

test_verifier in ubuntu_bpf with Jammy AWS / Azure / GCP / GKE 5.15 is failing with just 3 test cases:

  #27/u atomic compare-and-exchange smoketest - 32bit FAIL
  Unexpected success to load!
  verification time 34 usec
  stack depth 4
  processed 23 insns (limit 1000000) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1

  #30/u BPF_W cmpxchg should zero top 32 bits FAIL
  Unexpected success to load!
  verification time 21 usec
  stack depth 8
  processed 13 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 0

  #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL
  Unexpected verifier log!
  EXP: arg#0 pointer type STRUCT prog_test_ref_kfunc must point
  RES:
  FAIL
  Unexpected error message!
      EXP: arg#0 pointer type STRUCT prog_test_ref_kfunc must point
      RES: kernel btf_id 0 is not a function
  verification time 10 usec
  stack depth 0
  processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0

  kernel btf_id 0 is not a function
  verification time 10 usec
  stack depth 0
  processed 0 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0

Po-Hsu Lin (cypressyew)
description: updated
Po-Hsu Lin (cypressyew)
summary: - test_verifier in ubuntu_bpf failed with 3 test cases on J-AWS (#27, #30,
- #150)
+ test_verifier in ubuntu_bpf failed with 3 test cases on J-AWS / J-Azure
+ / J-GCP / J-GKE (#27, #30, #150)
Po-Hsu Lin (cypressyew)
description: updated
Po-Hsu Lin (cypressyew)
description: updated
Po-Hsu Lin (cypressyew)
summary: test_verifier in ubuntu_bpf failed with 3 test cases on J-AWS / J-Azure
- / J-GCP / J-GKE (#27, #30, #150)
+ / J-GCP / J-GKE (#27, #30, #150) AMD64
Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: test_verifier in ubuntu_bpf failed with 3 test cases on J-AWS / J-Azure / J-GCP / J-GKE (#27, #30, #150) AMD64
Download full text (9.9 KiB)

For ARM64, there will be more failures (40 failures):
 #21/u BPF_ATOMIC_AND without fetch FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 11 usec
 stack depth 8
 processed 12 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #21/p BPF_ATOMIC_AND without fetch FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 11 usec
 stack depth 8
 processed 10 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #22/u BPF_ATOMIC_AND with fetch FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 13 usec
 stack depth 8
 processed 16 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #22/p BPF_ATOMIC_AND with fetch FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 9 usec
 stack depth 8
 processed 14 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #23/u BPF_ATOMIC_AND with fetch 32bit FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 15 usec
 stack depth 4
 processed 14 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #23/p BPF_ATOMIC_AND with fetch 32bit FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 14 usec
 stack depth 4
 processed 14 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 10 usec
 stack depth 8
 processed 12 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 9 usec
 stack depth 8
 processed 12 insns (limit 1000000) max_states_per_insn 0 total_states 1 peak_states 1 mark_read 1
 #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 6 usec
 stack depth 8
 processed 6 insns (limit 1000000) max_states_per_insn 0 total_states 0 peak_states 0 mark_read 0
 #26/u atomic compare-and-exchange smoketest - 64bit FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 16 usec
 stack depth 8
 processed 23 insns (limit 1000000) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1
 #26/p atomic compare-and-exchange smoketest - 64bit FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 13 usec
 stack depth 8
 processed 23 insns (limit 1000000) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1
 #27/u atomic compare-and-exchange smoketest - 32bit FAIL
 Unexpected verifier log!
 EXP: R0 leaks addr into mem
 RES:
 FAIL
 Unexpected error message!
     EXP: R0 leaks addr into mem
     RES: verification time 23 usec
 stack depth 4
 processed 23 insns (limit 1000000) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1

 verification time 23 usec
 stack depth 4
 processed 23 insns (limit 1000000) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1
 #27/p atomic compare-and-exchange smoketest - 32bit FAIL
 Failed to load prog 'Unknown error 524'!
 verification time 20 usec
 sta...

Po-Hsu Lin (cypressyew)
summary: - test_verifier in ubuntu_bpf failed with 3 test cases on J-AWS / J-Azure
- / J-GCP / J-GKE (#27, #30, #150) AMD64
+ test_verifier in ubuntu_bpf failed with 3 test cases (#27, #30, #150) on
+ J-AMD64
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

For comment 1, I will track it in bug 1991215, let's make this one specific to AMD64.

tags: added: amd64
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.