bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH 4.19 0/9] bpf: fix verifier selftests on inefficient unaligned access architectures
Date: Sat, 5 Jun 2021 15:16:44 +0800	[thread overview]
Message-ID: <70c92574-ab22-1a04-067e-4c933ef75a9a@loongson.cn> (raw)
In-Reply-To: <1622604473-781-1-git-send-email-yangtiezhu@loongson.cn>

On 06/02/2021 11:27 AM, Tiezhu Yang wrote:
> With the following patch series, all verifier selftests pass on the archs which
> select HAVE_EFFICIENT_UNALIGNED_ACCESS.
>
> [v2,4.19,00/19] bpf: fix verifier selftests, add CVE-2021-29155, CVE-2021-33200 fixes
> https://patchwork.kernel.org/project/netdevbpf/cover/20210528103810.22025-1-ovidiu.panait@windriver.com/
>
> But on inefficient unaligned access architectures, there still exist many failures,
> so some patches about F_NEEDS_EFFICIENT_UNALIGNED_ACCESS are also needed, backport
> to 4.19 with a minor context difference.
>
> This patch series is based on the series (all now queued up by greg k-h):
> "bpf: fix verifier selftests, add CVE-2021-29155, CVE-2021-33200 fixes".
>
> Björn Töpel (2):
>    selftests/bpf: add "any alignment" annotation for some tests
>    selftests/bpf: Avoid running unprivileged tests with alignment
>      requirements
>
> Daniel Borkmann (2):
>    bpf: fix test suite to enable all unpriv program types
>    bpf: test make sure to run unpriv test cases in test_verifier
>
> David S. Miller (4):
>    bpf: Add BPF_F_ANY_ALIGNMENT.
>    bpf: Adjust F_NEEDS_EFFICIENT_UNALIGNED_ACCESS handling in
>      test_verifier.c
>    bpf: Make more use of 'any' alignment in test_verifier.c
>    bpf: Apply F_NEEDS_EFFICIENT_UNALIGNED_ACCESS to more ACCEPT test
>      cases.
>
> Joe Stringer (1):
>    selftests/bpf: Generalize dummy program types
>
>   include/uapi/linux/bpf.h                    |  14 ++
>   kernel/bpf/syscall.c                        |   7 +-
>   kernel/bpf/verifier.c                       |   3 +
>   tools/include/uapi/linux/bpf.h              |  14 ++
>   tools/lib/bpf/bpf.c                         |   8 +-
>   tools/lib/bpf/bpf.h                         |   2 +-
>   tools/testing/selftests/bpf/test_align.c    |   4 +-
>   tools/testing/selftests/bpf/test_verifier.c | 224 ++++++++++++++++++++--------
>   8 files changed, 206 insertions(+), 70 deletions(-)
>

Hi Greg and Sasha,

Could you please apply this series to 4.19?
Any comments will be much appreciated.

Thanks,
Tiezhu


  parent reply	other threads:[~2021-06-05  7:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  3:27 [PATCH 4.19 0/9] bpf: fix verifier selftests on inefficient unaligned access architectures Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 1/9] bpf: fix test suite to enable all unpriv program types Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 2/9] bpf: test make sure to run unpriv test cases in test_verifier Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 3/9] selftests/bpf: Generalize dummy program types Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 4/9] bpf: Add BPF_F_ANY_ALIGNMENT Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 5/9] bpf: Adjust F_NEEDS_EFFICIENT_UNALIGNED_ACCESS handling in test_verifier.c Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 6/9] bpf: Make more use of 'any' alignment " Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 7/9] bpf: Apply F_NEEDS_EFFICIENT_UNALIGNED_ACCESS to more ACCEPT test cases Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 8/9] selftests/bpf: add "any alignment" annotation for some tests Tiezhu Yang
2021-06-02  3:27 ` [PATCH 4.19 9/9] selftests/bpf: Avoid running unprivileged tests with alignment requirements Tiezhu Yang
2021-06-05  7:16 ` Tiezhu Yang [this message]
2021-06-08 14:40   ` [PATCH 4.19 0/9] bpf: fix verifier selftests on inefficient unaligned access architectures Greg Kroah-Hartman
2021-06-08 14:45 ` Greg Kroah-Hartman

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=70c92574-ab22-1a04-067e-4c933ef75a9a@loongson.cn \
    --to=yangtiezhu@loongson.cn \
    --cc=bpf@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).