From: Jiri Olsa <olsajiri@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: Wed, 30 Aug 2023 23:07:06 +0200 [thread overview]
Message-ID: <ZO+vetPCpOOCGitL@krava> (raw)
In-Reply-To: <ZO+RQwJhPhYcNGAi@krava>
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
jirka
>
> jirka
>
>
> ---
> [ 1022.710250][ T2556] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b6b73: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC NOPTI^M
> [ 1022.711206][ T2556] CPU: 2 PID: 2556 Comm: kworker/2:4 Tainted: G OE 6.5.0+ #693 1723c8b9805ff5a1672ab7e6f25977078a7bcceb^M
> [ 1022.712120][ T2556] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014^M
> [ 1022.712830][ T2556] Workqueue: events sk_psock_backlog^M
> [ 1022.713262][ T2556] RIP: 0010:skb_dequeue+0x4c/0x80^M
> [ 1022.713653][ T2556] Code: 41 48 85 ed 74 3c 8b 43 10 4c 89 e7 83 e8 01 89 43 10 48 8b 45 08 48 8b 55 00 48 c7 45 08 00 00 00 00 48 c7 45 00 00 00 00 00 <48> 89 42 08 48 89 10 e8 e8 6a 41 00 48 89 e8 5b 5d 41 5c c3 cc cc^M
> [ 1022.714963][ T2556] RSP: 0018:ffffc90003ca7dd0 EFLAGS: 00010046^M
> [ 1022.715431][ T2556] RAX: 6b6b6b6b6b6b6b6b RBX: ffff88811de269d0 RCX: 0000000000000000^M
> [ 1022.716068][ T2556] RDX: 6b6b6b6b6b6b6b6b RSI: 0000000000000282 RDI: ffff88811de269e8^M
> [ 1022.716676][ T2556] RBP: ffff888141ae39c0 R08: 0000000000000001 R09: 0000000000000000^M
> [ 1022.717283][ T2556] R10: 0000000000000001 R11: 0000000000000000 R12: ffff88811de269e8^M
> [ 1022.717930][ T2556] R13: 0000000000000001 R14: ffff888141ae39c0 R15: ffff88810a20e640^M
> [ 1022.718549][ T2556] FS: 0000000000000000(0000) GS:ffff88846d600000(0000) knlGS:0000000000000000^M
> [ 1022.719241][ T2556] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033^M
> [ 1022.719761][ T2556] CR2: 00007fb5c25ca000 CR3: 000000012b902004 CR4: 0000000000770ee0^M
> [ 1022.720394][ T2556] PKRU: 55555554^M
> [ 1022.720699][ T2556] Call Trace:^M
> [ 1022.720984][ T2556] <TASK>^M
> [ 1022.721254][ T2556] ? die_addr+0x32/0x80^M
> [ 1022.721589][ T2556] ? exc_general_protection+0x25a/0x4b0^M
> [ 1022.722026][ T2556] ? asm_exc_general_protection+0x22/0x30^M
> [ 1022.722489][ T2556] ? skb_dequeue+0x4c/0x80^M
> [ 1022.722854][ T2556] sk_psock_backlog+0x27a/0x300^M
> [ 1022.723243][ T2556] process_one_work+0x2a7/0x5b0^M
> [ 1022.723633][ T2556] worker_thread+0x4f/0x3a0^M
> [ 1022.723998][ T2556] ? __pfx_worker_thread+0x10/0x10^M
> [ 1022.724386][ T2556] kthread+0xfd/0x130^M
> [ 1022.724709][ T2556] ? __pfx_kthread+0x10/0x10^M
> [ 1022.725066][ T2556] ret_from_fork+0x2d/0x50^M
> [ 1022.725409][ T2556] ? __pfx_kthread+0x10/0x10^M
> [ 1022.725799][ T2556] ret_from_fork_asm+0x1b/0x30^M
> [ 1022.726201][ T2556] </TASK>^M
next prev parent reply other threads:[~2023-08-30 21:21 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 [this message]
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
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=ZO+vetPCpOOCGitL@krava \
--to=olsajiri@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.