Messages in this thread | | | Date | Tue, 23 Aug 2022 09:04:08 +0200 | From | Greg KH <> | Subject | Re: bpf selftest failed in 5.4.210 kernel |
| |
On Mon, Aug 22, 2022 at 10:23:02PM +0300, RAJESH DASARI wrote: > Hi, > > Please find the test scenarios which I have tried. > > Test 1: > > Running system Kernel version (tag/commit) : v5.4.210 > Kernel source code checkout : v5.4.210 > test_align test case execution status : Failure > > Test 2: > > Running system Kernel version (tag/commit) : v5.4.210 > Kernel source code checkout : v5.4.209 > test_align test case execution status : Failure > > Test 3: > > Running system Kernel version (tag/commit) : v5.4.209 > Kernel source code checkout : v5.4.209 > test_align test case execution status : Success > > Test 4: > > Running system Kernel version (tag/commit) : ACPI: APEI: Better fix to > avoid spamming the console with old error logs ( Kernel compiled at > this commit and system is booted with this change) > Kernel source code checkout : v5.4.210 but reverted selftests/bpf: Fix > test_align verifier log patterns and selftests/bpf: Fix "dubious > pointer arithmetic" test. If I revert only the Fix "dubious pointer > arithmetic" test, the testcase still fails. > test_align test case execution status : Success > > Test 5: > > Running system Kernel version (tag/commit) : v5.4.210 but reverted > commit (bpf: Verifer, adjust_scalar_min_max_vals to always call > update_reg_bounds() ) > Kernel source code checkout : v5.4.210 but reverted selftests/bpf: Fix > test_align verifier log patterns and selftests/bpf: Fix "dubious > pointer arithmetic" test. > test_align test case execution status : Success > > Test 6 : > > Running system Kernel version (tag/commit) : bpf: Test_verifier, #70 > error message updates for 32-bit right shift( Kernel compiled at this > commit and system is booted with this change) > Kernel source code checkout : v5.4.209 or v5.4.210 > test_align test case execution status : Failure
I'm sorry, but I don't know what to do with this report at all.
Is there some failure somewhere? If you use 'git bisect' do you find the offending commit?
confused,
greg k-h
| |