public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Geliang Tang <geliang.tang@suse.com>
Cc: "ast@kernel.org" <ast@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"memxor@gmail.com" <memxor@gmail.com>,
	"sashal@kernel.org" <sashal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Guoqing Jiang <guoqing.jiang@suse.com>,
	Kai Liu <kai.liu@suse.com>
Subject: Re: [PATCH 5.10 37/71] selftests/bpf: Add test for bpf_timer overwriting crash
Date: Mon, 21 Mar 2022 13:46:29 +0100	[thread overview]
Message-ID: <YjhzpQgUR06JGYdG@kroah.com> (raw)
In-Reply-To: <HE1PR0402MB3497CB13A12C4D15D20A1FCCF8139@HE1PR0402MB3497.eurprd04.prod.outlook.com>

On Fri, Mar 18, 2022 at 02:42:49PM +0000, Geliang Tang wrote:
> Hi Greg,
> 
> I got this bpf selftests build break today on the stable branch 5.10.106:
> 
> =========================================================================
> CLNG-LLC [test_maps] test_tracepoint.o
> progs/timer_crash.c:8:19: error: field has incomplete type 'struct bpf_timer'
>         struct bpf_timer timer;
>                          ^
> progs/timer_crash.c:8:9: note: forward declaration of 'struct bpf_timer'
>         struct bpf_timer timer;
>                ^
> progs/timer_crash.c:35:6: warning: implicit declaration of function 'bpf_get_current_task_btf' is invalid in C99 [-Wimplicit-function-declaration]
>         if (bpf_get_current_task_btf()->tgid != pid)
>             ^
> progs/timer_crash.c:35:34: error: member reference type 'int' is not a pointer
>         if (bpf_get_current_task_btf()->tgid != pid)
>             ~~~~~~~~~~~~~~~~~~~~~~~~~~  ^
> progs/timer_crash.c:49:3: warning: implicit declaration of function 'bpf_timer_cancel' is invalid in C99 [-Wimplicit-function-declaration]
>                 bpf_timer_cancel(&e->timer);
>                 ^
> 2 warnings and 2 errors generated.
>   CLNG-LLC [test_maps] test_trace_ext_tracing.o
> llc: error: llc: <stdin>:1:1: error: expected top-level entity
> BPF obj compilation failed
> ^
> make: *** [Makefile:402: tools/testing/selftests/bpf/timer_crash.o] Error 1
> make: *** Waiting for unfinished jobs....
>   CLNG-LLC [test_maps] test_trace_ext.o
> =========================================================================
> 
> It is introduced by this commit, "selftests/bpf: Add test for bpf_timer
> overwriting crash". Since the commit "bpf: Introduce bpf timers." has not
> been merged into the stable branch yet.
> 
> I am writing to you to report this bug.
> 

Now reverted, thanks!

greg k-h

       reply	other threads:[~2022-03-21 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <HE1PR0402MB3497CB13A12C4D15D20A1FCCF8139@HE1PR0402MB3497.eurprd04.prod.outlook.com>
2022-03-21 12:46 ` gregkh [this message]
2022-03-14 11:52 [PATCH 5.10 00/71] 5.10.106-rc1 review Greg Kroah-Hartman
2022-03-14 11:53 ` [PATCH 5.10 37/71] selftests/bpf: Add test for bpf_timer overwriting crash 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=YjhzpQgUR06JGYdG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ast@kernel.org \
    --cc=geliang.tang@suse.com \
    --cc=guoqing.jiang@suse.com \
    --cc=kai.liu@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=memxor@gmail.com \
    --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