From: Greg KH <gregkh@linuxfoundation.org>
To: Po-Hsu Lin <po-hsu.lin@canonical.com>
Cc: stable@vger.kernel.org, memxor@gmail.com,
linux-kernel@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH stable 5.15 1/1] selftests/bpf: Add test_verifier support to fixup kfunc call insns
Date: Mon, 4 Jul 2022 16:46:15 +0200 [thread overview]
Message-ID: <YsL9N8ItUlQaevCs@kroah.com> (raw)
In-Reply-To: <20220701130858.282569-2-po-hsu.lin@canonical.com>
On Fri, Jul 01, 2022 at 09:08:58PM +0800, Po-Hsu Lin wrote:
> From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
>
> commit 0201b80772ac2b712bbbfe783cdb731fdfb4247e upstream.
>
> This allows us to add tests (esp. negative tests) where we only want to
> ensure the program doesn't pass through the verifier, and also verify
> the error. The next commit will add the tests making use of this.
>
> Signed-off-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> Link: https://lore.kernel.org/r/20220114163953.1455836-9-memxor@gmail.com
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> [PHLin: backport due to lack of fixup_map_timer]
> Signed-off-by: Po-Hsu Lin <po-hsu.lin@canonical.com>
> ---
> tools/testing/selftests/bpf/test_verifier.c | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-07-04 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 13:08 [PATCH stable 5.15 0/1] Fix bpf selftest build failure - error: 'struct bpf_test' has no member named 'fixup_kfunc_btf_id' Po-Hsu Lin
2022-07-01 13:08 ` [PATCH stable 5.15 1/1] selftests/bpf: Add test_verifier support to fixup kfunc call insns Po-Hsu Lin
2022-07-04 14:46 ` 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=YsL9N8ItUlQaevCs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=po-hsu.lin@canonical.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;
as well as URLs for NNTP newsgroup(s).