Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pu Lehui <pulehui@huawei.com>
Cc: Pu Lehui <pulehui@huaweicloud.com>,
	stable@vger.kernel.org, Eduard Zingerman <eddyz87@gmail.com>,
	Luiz Capitulino <luizcap@amazon.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH 5.10 0/6] Backporting for test_verifier failed
Date: Wed, 2 Aug 2023 09:28:23 +0200	[thread overview]
Message-ID: <2023080230-absence-angriness-141b@gregkh> (raw)
In-Reply-To: <fe95523c-1adb-c1b8-4259-1e939eff931c@huawei.com>

On Wed, Aug 02, 2023 at 03:23:14PM +0800, Pu Lehui wrote:
> Add CC gregkh@linuxfoundation.org

Why?

> I am not sure if the email address of <greg@kroah.com> is valid

It is.

> On 2023/8/1 22:36, Pu Lehui wrote:
> > Luiz Capitulino reported the test_verifier test failed:
> > "precise: ST insn causing spi > allocated_stack".
> > And it was introduced by the following upstream commit:
> > ecdf985d7615 ("bpf: track immediate values written to stack by BPF_ST instruction")
> > 
> > Eduard's investigation [4] shows that test failure is not a bug, but a
> > difference in BPF verifier behavior between upstream, where commits
> > [1,2,3] by Andrii are present, and 5.10, where these commits are absent.
> > 
> > Backporting strategy is consistent with Eduard in kernel version 6.1 [5],
> > but with some conflicts in patch #1, #4 and #6 due to the bpf of 5.10
> > doesn't support more features. Both test_verifier and test_maps have
> > passed, while test_progs and test_progs-no_alu32 with no new failure
> > ceses.
> > 
> > Commits of Andrii:
> > [1] be2ef8161572 ("bpf: allow precision tracking for programs with subprogs")
> > [2] f63181b6ae79 ("bpf: stop setting precise in current state")
> > [3] 7a830b53c17b ("bpf: aggressively forget precise markings during state checkpointing")
> > 
> > Links:
> > [4] https://lore.kernel.org/stable/c9b10a8a551edafdfec855fbd35757c6238ad258.camel@gmail.com/
> > [5] https://lore.kernel.org/all/20230724124223.1176479-2-eddyz87@gmail.com/
> > 
> > Andrii Nakryiko (4):
> >    bpf: allow precision tracking for programs with subprogs
> >    bpf: stop setting precise in current state
> >    bpf: aggressively forget precise markings during state checkpointing
> >    selftests/bpf: make test_align selftest more robust
> > 
> > Ilya Leoshkevich (1):
> >    selftests/bpf: Fix sk_assign on s390x
> > 
> > Yonghong Song (1):
> >    selftests/bpf: Workaround verification failure for
> >      fexit_bpf2bpf/func_replace_return_code
> > 
> >   kernel/bpf/verifier.c                         | 175 ++++++++++++++++--
> >   .../testing/selftests/bpf/prog_tests/align.c  |  36 ++--
> >   .../selftests/bpf/prog_tests/sk_assign.c      |  25 ++-
> >   .../selftests/bpf/progs/connect4_prog.c       |   2 +-
> >   .../selftests/bpf/progs/test_sk_assign.c      |  11 ++
> >   .../bpf/progs/test_sk_assign_libbpf.c         |   3 +
> >   6 files changed, 219 insertions(+), 33 deletions(-)
> >   create mode 100644 tools/testing/selftests/bpf/progs/test_sk_assign_libbpf.c
> > 

What is the question here for me?

confused,

greg k-h

  reply	other threads:[~2023-08-02  7:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 14:36 [PATCH 5.10 0/6] Backporting for test_verifier failed Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 1/6] bpf: allow precision tracking for programs with subprogs Pu Lehui
2023-08-04 10:33   ` Greg KH
2023-08-04 12:15     ` Pu Lehui
2023-08-04 12:18       ` Eduard Zingerman
2023-08-04 12:34         ` Pu Lehui
2023-08-04 18:56     ` Thorsten Leemhuis
2023-08-05  5:47       ` Greg KH
2023-08-01 14:36 ` [PATCH 5.10 2/6] bpf: stop setting precise in current state Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 3/6] bpf: aggressively forget precise markings during state checkpointing Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 4/6] selftests/bpf: make test_align selftest more robust Pu Lehui
2023-08-01 14:36 ` [PATCH 5.10 5/6] selftests/bpf: Workaround verification failure for fexit_bpf2bpf/func_replace_return_code Pu Lehui
2023-08-01 14:37 ` [PATCH 5.10 6/6] selftests/bpf: Fix sk_assign on s390x Pu Lehui
2023-08-02  7:23 ` [PATCH 5.10 0/6] Backporting for test_verifier failed Pu Lehui
2023-08-02  7:28   ` Greg KH [this message]
2023-08-02 19:28 ` Luiz Capitulino

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=2023080230-absence-angriness-141b@gregkh \
    --to=greg@kroah.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=luizcap@amazon.com \
    --cc=pulehui@huawei.com \
    --cc=pulehui@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox