From: Cong Wang <xiyou.wangcong@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andriin@fb.com>,
"Paolo Abeni" <pabeni@redhat.com>, bpf <bpf@vger.kernel.org>,
"Linux Kernel Network Developers" <netdev@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>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Jiri Benc" <jbenc@redhat.com>,
"Yauheni Kaliuta" <yauheni.kaliuta@redhat.com>
Subject: Re: WARNING net/core/stream.c:208 when running test_sockmap
Date: Wed, 7 Apr 2021 16:14:27 -0700 [thread overview]
Message-ID: <CAM_iQpUdbsf97g8X=K7wKnGu1mmfuu7bseHdtaQ_uvo1XOmG_A@mail.gmail.com> (raw)
In-Reply-To: <YG3SuK4W/N9jqknL@krava>
On Wed, Apr 7, 2021 at 2:22 PM Jiri Olsa <jolsa@redhat.com> wrote:
>
> hi,
> I'm getting couple of WARNINGs below when running
> test_sockmap on latest bpf-next/master, like:
>
> # while :; do ./test_sockmap ; done
>
> The warning is at:
> WARN_ON(sk->sk_forward_alloc);
>
> so looks like some socket allocation math goes wrong.
This one should be fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=144748eb0c445091466c9b741ebd0bfcc5914f3d
So please try the latest bpf branch.
Thanks.
next parent reply other threads:[~2021-04-07 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YG3SuK4W/N9jqknL@krava>
2021-04-07 23:14 ` Cong Wang [this message]
2021-04-08 10:12 ` WARNING net/core/stream.c:208 when running test_sockmap Jiri Olsa
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='CAM_iQpUdbsf97g8X=K7wKnGu1mmfuu7bseHdtaQ_uvo1XOmG_A@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jbenc@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=songliubraving@fb.com \
--cc=toke@redhat.com \
--cc=yauheni.kaliuta@redhat.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).