From: Eduard Zingerman <eddyz87@gmail.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Martin KaFai Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Hou Tao <houtao1@huawei.com>
Subject: Re: [BUG bpf-next] bpf/net: Hitting gpf when running selftests
Date: Thu, 31 Aug 2023 18:03:04 +0300 [thread overview]
Message-ID: <082a6db6838d3aee5ca39eabd35d4da0c9691a0d.camel@gmail.com> (raw)
In-Reply-To: <de816b89073544deb2ce34c4b242d583a6d4660f.camel@gmail.com>
On Thu, 2023-08-31 at 13:52 +0300, Eduard Zingerman wrote:
> On Wed, 2023-08-30 at 23:07 +0200, Jiri Olsa wrote:
> > On Wed, Aug 30, 2023 at 08:58:11PM +0200, Jiri Olsa wrote:
> > > hi,
> > > I'm hitting crash below on bpf-next/master when running selftests,
> > > full log and config attached
> >
> > it seems to be 'test_progs -t sockmap_listen' triggering that
>
> Hi,
>
> I hit it as well, use the following command to reproduce:
>
> for i in $(seq 1 100); do \
> ./test_progs -a 'sockmap_listen/sockmap VSOCK test_vsock_redir' \
> | grep Summary; \
> done
>
For what its worth, bisect points to the following commit:
147f3efaa241 ("sched/fair: Implement an EEVDF-like scheduling policy")
Which was merged into bpf-next 3 days ago as a part of:
3ca9a836ff53 ("Merge tag 'sched-core-2023-08-28' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip")
Scheduling changes uncovered some old race condition?
[...]
next prev parent reply other threads:[~2023-08-31 15:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 18:58 [BUG bpf-next] bpf/net: Hitting gpf when running selftests Jiri Olsa
2023-08-30 21:07 ` Jiri Olsa
2023-08-31 9:46 ` Xu Kuohai
2023-08-31 15:23 ` Xu Kuohai
2023-08-31 19:19 ` John Fastabend
2023-08-31 20:20 ` John Fastabend
2023-09-01 9:10 ` Xu Kuohai
2023-09-01 9:32 ` Jiri Olsa
2023-09-01 20:22 ` John Fastabend
2023-08-31 10:52 ` Eduard Zingerman
2023-08-31 15:03 ` Eduard Zingerman [this message]
2023-08-31 15:34 ` Xu Kuohai
2023-08-31 15:43 ` Eduard Zingerman
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=082a6db6838d3aee5ca39eabd35d4da0c9691a0d.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--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;
as well as URLs for NNTP newsgroup(s).