From: Simon Horman <horms@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
kuba@kernel.org, neilb@suse.de, jlayton@kernel.org,
kolga@netapp.com, Dai.Ngo@oracle.com, tom@talpey.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Lex Siegel <usiegl00@gmail.com>
Subject: Re: [PATCH net v2] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
Date: Mon, 1 Jul 2024 11:57:42 +0100 [thread overview]
Message-ID: <20240701105742.GV17134@kernel.org> (raw)
In-Reply-To: <Zn7wtStV+iafWRXj@tissot.1015granger.net>
On Fri, Jun 28, 2024 at 01:19:49PM -0400, Chuck Lever wrote:
> On Fri, Jun 28, 2024 at 06:31:23PM +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>
> > 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. ]
> >
> > v1 -> v2:
> > - Plain resend, adding more sunrpc folks to Cc
> >
> > 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.
> > --
> > 2.21.0
> >
>
> Hi Daniel -
>
> I know this is not documented in MAINTAINERS, but changes to
> net/sunrpc/xprtsock.c go to Anna Schumaker and Trond Myklebust,
> cc: linux-nfs@vger.
Would it be possible to update MAINTAINERS accordingly?
next prev parent reply other threads:[~2024-07-01 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 16:31 [PATCH net v2] net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket Daniel Borkmann
2024-07-03 7:01 ` [PATCH net v3] " Daniel Borkmann
2024-06-28 20:35 ` Daniel Borkmann
2024-06-28 17:19 ` [PATCH net v2] " Chuck Lever
2024-07-01 10:57 ` Simon Horman [this message]
2024-07-01 14:04 ` Chuck Lever III
2024-07-02 12:46 ` Simon Horman
2024-07-02 12:56 ` Fwd: " Chuck Lever III
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=20240701105742.GV17134@kernel.org \
--to=horms@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=bpf@vger.kernel.org \
--cc=chuck.lever@oracle.com \
--cc=daniel@iogearbox.net \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=kuba@kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--cc=tom@talpey.com \
--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 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.