From: Paolo Abeni <pabeni@redhat.com>
To: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Cc: netdev@vger.kernel.org, linux-nfs@vger.kernel.org,
Lex Siegel <usiegl00@gmail.com>, Neil Brown <neilb@suse.de>,
Daniel Borkmann <daniel@iogearbox.net>,
kuba@kernel.org
Subject: Re: [PATCH net v3 resend] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
Date: Tue, 09 Jul 2024 10:22:21 +0200 [thread overview]
Message-ID: <d8656bf85a142aae001e4275fcbc195fa2da8473.camel@redhat.com> (raw)
In-Reply-To: <9069ec1d59e4b2129fc23433349fd5580ad43921.1720075070.git.daniel@iogearbox.net>
On Thu, 2024-07-04 at 08:41 +0200, Daniel Borkmann 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.
>
> ECONNREFUSED as error seems reasonable. For programs setting a different error
> can be out of reach (see handling in 4fbac77d2d09) in particular on kernels
> which do not have f10d05966196 ("bpf: Make BPF_PROG_RUN_ARRAY return -err
> instead of allow boolean"), thus given that it is better to simply remap for
> consistent behavior. UDP does handle EPERM in xs_udp_send_request().
>
> Fixes: d74bad4e74ee ("bpf: Hooks for sys_connect")
> Fixes: 4fbac77d2d09 ("bpf: Hooks for sys_bind")
> Co-developed-by: Lex Siegel <usiegl00@gmail.com>
> Signed-off-by: Lex Siegel <usiegl00@gmail.com>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Neil Brown <neilb@suse.de>
> Cc: Trond Myklebust <trondmy@kernel.org>
> Cc: Anna Schumaker <anna@kernel.org>
> Link: https://github.com/cilium/cilium/issues/33395
> Link: https://lore.kernel.org/bpf/171374175513.12877.8993642908082014881@noble.neil.brown.name
> ---
> [ Fixes tags are set to the orig connect commit so that stable team
> can pick this up.
>
> Resend as it turns out that patchwork did not pick up the earlier
> resends likely due to the message id being the same. ]
>
> v1 -> v2 -> v3:
> - Plain resend, adding correct sunrpc folks to Cc
> https://lore.kernel.org/bpf/Zn7wtStV+iafWRXj@tissot.1015granger.net/
>
> net/sunrpc/xprtsock.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/net/sunrpc/xprtsock.c b/net/sunrpc/xprtsock.c
> index dfc353eea8ed..0e1691316f42 100644
> --- a/net/sunrpc/xprtsock.c
> +++ b/net/sunrpc/xprtsock.c
> @@ -2441,6 +2441,13 @@ static void xs_tcp_setup_socket(struct work_struct *work)
> transport->srcport = 0;
> status = -EAGAIN;
> break;
> + case -EPERM:
> + /* Happens, for instance, if a BPF program is preventing
> + * the connect. Remap the error so upper layers can better
> + * deal with it.
> + */
> + status = -ECONNREFUSED;
> + fallthrough;
> case -EINVAL:
> /* Happens, for instance, if the user specified a link
> * local IPv6 address without a scope-id.
The patch looks sane to me. @Trond, @Anna, are you ok for this to go
directly into the net tree?
Thanks!
Paolo
next prev parent reply other threads:[~2024-07-09 8:22 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 [this message]
2024-07-11 8:10 ` Paolo Abeni
2024-07-11 10:30 ` patchwork-bot+netdevbpf
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=d8656bf85a142aae001e4275fcbc195fa2da8473.camel@redhat.com \
--to=pabeni@redhat.com \
--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