From: patchwork-bot+netdevbpf@kernel.org
To: wangyufen <wangyufen@huawei.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
john.fastabend@gmail.com, jakub@cloudflare.com
Subject: Re: [PATCH net v3] bpf, sockmap: fix the sk->sk_forward_alloc warning of sk_stream_kill_queues()
Date: Tue, 01 Nov 2022 21:10:15 +0000 [thread overview]
Message-ID: <166733701586.25446.5024409898528693379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1667266296-8794-1-git-send-email-wangyufen@huawei.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 1 Nov 2022 09:31:36 +0800 you wrote:
> When running `test_sockmap` selftests, got the following warning:
>
> WARNING: CPU: 2 PID: 197 at net/core/stream.c:205 sk_stream_kill_queues+0xd3/0xf0
> Call Trace:
> <TASK>
> inet_csk_destroy_sock+0x55/0x110
> tcp_rcv_state_process+0xd28/0x1380
> ? tcp_v4_do_rcv+0x77/0x2c0
> tcp_v4_do_rcv+0x77/0x2c0
> __release_sock+0x106/0x130
> __tcp_close+0x1a7/0x4e0
> tcp_close+0x20/0x70
> inet_release+0x3c/0x80
> __sock_release+0x3a/0xb0
> sock_close+0x14/0x20
> __fput+0xa3/0x260
> task_work_run+0x59/0xb0
> exit_to_user_mode_prepare+0x1b3/0x1c0
> syscall_exit_to_user_mode+0x19/0x50
> do_syscall_64+0x48/0x90
> entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> [...]
Here is the summary with links:
- [net,v3] bpf, sockmap: fix the sk->sk_forward_alloc warning of sk_stream_kill_queues()
https://git.kernel.org/bpf/bpf/c/8ec95b94716a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-01 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 1:31 [PATCH net v3] bpf, sockmap: fix the sk->sk_forward_alloc warning of sk_stream_kill_queues() Wang Yufen
2022-11-01 21:10 ` patchwork-bot+netdevbpf [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=166733701586.25446.5024409898528693379.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=wangyufen@huawei.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