test_verifier in ubuntu_bpf failed with 40 test cases on J-ARM64

[Po-Hsu Lin]

With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf test can now be tested.

There are 40 failures discovered in test_verifier with ARM64 instances:
 #21/u BPF_ATOMIC_AND without fetch FAIL
 #21/p BPF_ATOMIC_AND without fetch FAIL
 #22/u BPF_ATOMIC_AND with fetch FAIL
 #22/p BPF_ATOMIC_AND with fetch FAIL
 #23/u BPF_ATOMIC_AND with fetch 32bit FAIL
 #23/p BPF_ATOMIC_AND with fetch 32bit FAIL
 #24/u BPF_ATOMIC_AND with fetch - r0 as source reg FAIL
 #24/p BPF_ATOMIC_AND with fetch - r0 as source reg FAIL
 #25/p BPF_ATOMIC bounds propagation, mem->reg FAIL
 #26/u atomic compare-and-exchange smoketest - 64bit FAIL
 #26/p atomic compare-and-exchange smoketest - 64bit FAIL
 #27/u atomic compare-and-exchange smoketest - 32bit FAIL
 #27/p atomic compare-and-exchange smoketest - 32bit FAIL
 #30/u BPF_W cmpxchg should zero top 32 bits FAIL
 #30/p BPF_W cmpxchg should zero top 32 bits FAIL
 #31/p Dest pointer in r0 - succeed, check 2 FAIL
 #33/p Dest pointer in r0 - succeed, check 4 FAIL
 #35/u BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL
 #35/p BPF_ATOMIC_FETCH_ADD smoketest - 64bit FAIL
 #36/u BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL
 #36/p BPF_ATOMIC_FETCH_ADD smoketest - 32bit FAIL
 #41/u BPF_ATOMIC OR without fetch FAIL
 #41/p BPF_ATOMIC OR without fetch FAIL
 #42/u BPF_ATOMIC OR with fetch FAIL
 #42/p BPF_ATOMIC OR with fetch FAIL
 #43/u BPF_ATOMIC OR with fetch 32bit FAIL
 #43/p BPF_ATOMIC OR with fetch 32bit FAIL
 #44/u BPF_W atomic_fetch_or should zero top 32 bits FAIL
 #44/p BPF_W atomic_fetch_or should zero top 32 bits FAIL
 #45/u atomic exchange smoketest - 64bit FAIL
 #45/p atomic exchange smoketest - 64bit FAIL
 #46/u atomic exchange smoketest - 32bit FAIL
 #46/p atomic exchange smoketest - 32bit FAIL
 #47/u BPF_ATOMIC XOR without fetch FAIL
 #47/p BPF_ATOMIC XOR without fetch FAIL
 #48/u BPF_ATOMIC XOR with fetch FAIL
 #48/p BPF_ATOMIC XOR with fetch FAIL
 #49/u BPF_ATOMIC XOR with fetch 32bit FAIL
 #49/p BPF_ATOMIC XOR with fetch 32bit FAIL
 #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL

For failures with AMD64 instance, please refer to bug 1991351

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1991215

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Po-Hsu Lin (cypressyew)]

For AWS / Azure / GCP / GKE, they are just failing with 3 failures:
  #27/u atomic compare-and-exchange smoketest - 32bit FAIL
  #30/u BPF_W cmpxchg should zero top 32 bits FAIL
  #150/p calls: trigger reg2btf_ids[reg->type] for reg->type > __BPF_REG_TYPE_MAX FAIL

Please refer to bug 1991351

[Po-Hsu Lin (cypressyew)]

For comment 2, I found it's 3 failures for all of the AMD64 instances.

ARM64 instances on other clouds can fail with 40 failures like this here.
I will update the bug title / description.

[Magali Lemes do Sacramento (magalilemes)]

Found on Jammy 5.15.0-70.77+fips1 on openstack, 2023-03-20 cycle.