From: Greg KH <greg@kroah.com>
To: hsimeliere.opensource@witekio.com
Cc: stable@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Lex Siegel <usiegl00@gmail.com>, Neil Brown <neilb@suse.de>,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH v5.15-v5.4] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
Date: Tue, 10 Sep 2024 09:36:11 +0200 [thread overview]
Message-ID: <2024091004-finished-dupe-d9b2@gregkh> (raw)
In-Reply-To: <20240909161548.255373-1-hsimeliere.opensource@witekio.com>
On Mon, Sep 09, 2024 at 06:15:48PM +0200, hsimeliere.opensource@witekio.com wrote:
> From: Daniel Borkmann <daniel@iogearbox.net>
>
> commit 626dfed5fa3bfb41e0dffd796032b555b69f9cde upstream.
>
> 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
> Link: https://patch.msgid.link/9069ec1d59e4b2129fc23433349fd5580ad43921.1720075070.git.daniel@iogearbox.net
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> Signed-off-by: Hugo SIMELIERE <hsimeliere.opensource@witekio.com>
> ---
> net/sunrpc/xprtsock.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-09-10 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 16:15 [PATCH v5.15-v5.4] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket hsimeliere.opensource
2024-09-10 7:36 ` Greg KH [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=2024091004-finished-dupe-d9b2@gregkh \
--to=greg@kroah.com \
--cc=anna@kernel.org \
--cc=daniel@iogearbox.net \
--cc=hsimeliere.opensource@witekio.com \
--cc=neilb@suse.de \
--cc=pabeni@redhat.com \
--cc=stable@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