All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ovidiu Panait <ovidiu.panait@windriver.com>
Cc: stable@vger.kernel.org, raajeshdasari@gmail.com,
	jean-philippe@linaro.org
Subject: Re: [PATCH 4.19 0/2] bpf: fix test_verifier, test_align selftests
Date: Thu, 1 Sep 2022 12:09:52 +0200	[thread overview]
Message-ID: <YxCE8IvP3Xfn7QAV@kroah.com> (raw)
In-Reply-To: <20220829115054.1714528-1-ovidiu.panait@windriver.com>

On Mon, Aug 29, 2022 at 02:50:52PM +0300, Ovidiu Panait wrote:
> Backport of upstream commits [1] and [2] to 4.19-stable broke test_verifier and
> test_align bpf selftests.
> [1] 2fa7d94afc1a ("bpf: Fix the off-by-two error in range markings")
> [2] 294f2fc6da27 ("bpf: Verifer, adjust_scalar_min_max_vals to always call
>                    update_reg_bounds()")
> 
> This series fixes all failing test_verifier/test_align testcases for 4.19:
> root@intel-x86-64:~/bpf# ./test_verifier
> ...
> #664/p mov64 src == dst OK
> #665/p mov64 src != dst OK
> #666/u calls: ctx read at start of subprog OK
> #666/p calls: ctx read at start of subprog OK
> Summary: 932 PASSED, 0 SKIPPED, 0 FAILED
> 
> root@intel-x86-64:~/bpf# ./test_align
> Test   0: mov ... PASS
> Test   1: shift ... PASS
> Test   2: addsub ... PASS
> Test   3: mul ... PASS
> Test   4: unknown shift ... PASS
> Test   5: unknown mul ... PASS
> Test   6: packet const offset ... PASS
> Test   7: packet variable offset ... PASS
> Test   8: packet variable offset 2 ... PASS
> Test   9: dubious pointer arithmetic ... PASS
> Test  10: variable subtraction ... PASS
> Test  11: pointer variable subtraction ... PASS
> Results: 12 pass 0 fail
> 
> 
> Maxim Mikityanskiy (1):
>   bpf: Fix the off-by-two error in range markings
> 
> Stanislav Fomichev (1):
>   selftests/bpf: Fix test_align verifier log patterns
> 
>  tools/testing/selftests/bpf/test_align.c    | 27 ++++++++---------
>  tools/testing/selftests/bpf/test_verifier.c | 32 ++++++++++-----------
>  2 files changed, 30 insertions(+), 29 deletions(-)
> 
> -- 
> 2.37.2
> 

Now queued up, thanks!

greg k-h

      parent reply	other threads:[~2022-09-01 10:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 11:50 [PATCH 4.19 0/2] bpf: fix test_verifier, test_align selftests Ovidiu Panait
2022-08-29 11:50 ` [PATCH 4.19 1/2] bpf: Fix the off-by-two error in range markings Ovidiu Panait
2022-08-29 11:50 ` [PATCH 4.19 2/2] selftests/bpf: Fix test_align verifier log patterns Ovidiu Panait
2022-09-01 10:09 ` Greg KH [this message]

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=YxCE8IvP3Xfn7QAV@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jean-philippe@linaro.org \
    --cc=ovidiu.panait@windriver.com \
    --cc=raajeshdasari@gmail.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.