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,
daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
songliubraving@fb.com, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, shuah@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH stable 5.15 0/1] Revert "selftests/bpf: Add test for bpf_timer overwriting crash"
Date: Thu, 7 Jul 2022 20:05:11 +0200 [thread overview]
Message-ID: <YscgV2/HW35p4yyi@kroah.com> (raw)
In-Reply-To: <20220707094207.229875-1-po-hsu.lin@canonical.com>
On Thu, Jul 07, 2022 at 05:42:06PM +0800, Po-Hsu Lin wrote:
> The bpf_timer overwriting crash test will cause bpf selftest build
> fail on the stable 5.15 tree with:
>
> progs/timer_crash.c:8:19: error: field has incomplete type 'struct bpf_timer'
> struct bpf_timer timer;
> ^
> /home/ubuntu/linux/tools/testing/selftests/bpf/tools/include/bpf/bpf_helper_defs.h:39:8:
> note: forward declaration of 'struct bpf_timer'
> struct bpf_timer;
> ^
> 1 error generated.
>
> Test shows this can only be built with 5.17 and newer kernels. Let's
> revert it for the 5.15 tree.
>
> Po-Hsu Lin (1):
> Revert "selftests/bpf: Add test for bpf_timer overwriting crash"
>
> .../testing/selftests/bpf/prog_tests/timer_crash.c | 32 -------------
> tools/testing/selftests/bpf/progs/timer_crash.c | 54 ----------------------
> 2 files changed, 86 deletions(-)
> delete mode 100644 tools/testing/selftests/bpf/prog_tests/timer_crash.c
> delete mode 100644 tools/testing/selftests/bpf/progs/timer_crash.c
>
> --
> 2.7.4
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-07-07 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 9:42 [PATCH stable 5.15 0/1] Revert "selftests/bpf: Add test for bpf_timer overwriting crash" Po-Hsu Lin
2022-07-07 9:42 ` [PATCH stable 5.15 1/1] " Po-Hsu Lin
2022-07-07 18:05 ` 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=YscgV2/HW35p4yyi@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=po-hsu.lin@canonical.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=yhs@fb.com \
/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