From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
jakub@cloudflare.com, bpf@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: sockmap calling sleepable function in teardown path
Date: Tue, 28 Jun 2022 07:40:13 +0000 [thread overview]
Message-ID: <165640201315.9025.13424648170851367214.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220628035803.317876-1-john.fastabend@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 27 Jun 2022 20:58:03 -0700 you wrote:
> syzbot reproduced the BUG,
>
> BUG: sleeping function called from invalid context at kernel/workqueue.c:3010
>
> with the following stack trace fragment
>
> start_flush_work kernel/workqueue.c:3010 [inline]
> __flush_work+0x109/0xb10 kernel/workqueue.c:3074
> __cancel_work_timer+0x3f9/0x570 kernel/workqueue.c:3162
> sk_psock_stop+0x4cb/0x630 net/core/skmsg.c:802
> sock_map_destroy+0x333/0x760 net/core/sock_map.c:1581
> inet_csk_destroy_sock+0x196/0x440 net/ipv4/inet_connection_sock.c:1130
> __tcp_close+0xd5b/0x12b0 net/ipv4/tcp.c:2897
> tcp_close+0x29/0xc0 net/ipv4/tcp.c:2909
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: sockmap calling sleepable function in teardown path
https://git.kernel.org/bpf/bpf-next/c/697fb80a5364
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-06-28 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 3:58 [PATCH bpf-next] bpf: sockmap calling sleepable function in teardown path John Fastabend
2022-06-28 7:40 ` 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=165640201315.9025.13424648170851367214.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@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