From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org,
syzbot+df400f2f24a1677cd7e0@syzkaller.appspotmail.com,
vfedorenko@novek.ru, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] rxrpc: Fix deadlock around release of dst cached on udp tunnel
Date: Sat, 30 Jan 2021 05:50:06 +0000 [thread overview]
Message-ID: <161198580621.4523.3032466823859435462.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <161196443016.3868642.5577440140646403533.stgit@warthog.procyon.org.uk>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 29 Jan 2021 23:53:50 +0000 you wrote:
> AF_RXRPC sockets use UDP ports in encap mode. This causes socket and dst
> from an incoming packet to get stolen and attached to the UDP socket from
> whence it is leaked when that socket is closed.
>
> When a network namespace is removed, the wait for dst records to be cleaned
> up happens before the cleanup of the rxrpc and UDP socket, meaning that the
> wait never finishes.
>
> [...]
Here is the summary with links:
- [net] rxrpc: Fix deadlock around release of dst cached on udp tunnel
https://git.kernel.org/netdev/net/c/5399d52233c4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-01-30 5:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 23:53 [PATCH net] rxrpc: Fix deadlock around release of dst cached on udp tunnel David Howells
2021-01-30 5:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-29 16:44 David Howells
2021-01-29 17:30 ` Vadim Fedorenko
2021-01-29 17:36 ` Vadim Fedorenko
2021-01-29 17:41 ` David Howells
2021-01-29 19:53 ` Vadim Fedorenko
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=161198580621.4523.3032466823859435462.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+df400f2f24a1677cd7e0@syzkaller.appspotmail.com \
--cc=vfedorenko@novek.ru \
/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.