From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: kuba@kernel.org, netdev@vger.kernel.org,
linux-nfs@vger.kernel.org, usiegl00@gmail.com, neilb@suse.de,
trondmy@kernel.org, anna@kernel.org
Subject: Re: [PATCH net v3 resend] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
Date: Thu, 11 Jul 2024 10:30:28 +0000 [thread overview]
Message-ID: <172069382888.18320.4145482834911828098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9069ec1d59e4b2129fc23433349fd5580ad43921.1720075070.git.daniel@iogearbox.net>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 4 Jul 2024 08:41:57 +0200 you wrote:
> When using a BPF program on kernel_connect(), the call can return -EPERM. This
> causes xs_tcp_setup_socket() to loop forever, filling up the syslog and causing
> the kernel to potentially freeze up.
>
> Neil suggested:
>
> This will propagate -EPERM up into other layers which might not be ready
> to handle it. It might be safer to map EPERM to an error we would be more
> likely to expect from the network system - such as ECONNREFUSED or ENETDOWN.
>
> [...]
Here is the summary with links:
- [net,v3,resend] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
https://git.kernel.org/netdev/net/c/626dfed5fa3b
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:[~2024-07-11 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 6:41 [PATCH net v3 resend] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket Daniel Borkmann
2024-07-08 22:21 ` Daniel Borkmann
2024-07-09 8:22 ` Paolo Abeni
2024-07-11 8:10 ` Paolo Abeni
2024-07-11 10:30 ` 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=172069382888.18320.4145482834911828098.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anna@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kuba@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=trondmy@kernel.org \
--cc=usiegl00@gmail.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