From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <daan.j.demeyer@gmail.com>
Cc: <bpf@vger.kernel.org>, <kernel-team@meta.com>,
<martin.lau@linux.dev>, <netdev@vger.kernel.org>,
<kuniyu@amazon.com>
Subject: Re: [PATCH bpf-next v2] Only run BPF cgroup unix sockaddr recvmsg() hooks on named sockets
Date: Thu, 12 Oct 2023 11:11:42 -0700 [thread overview]
Message-ID: <20231012181142.60636-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20231012085216.219918-1-daan.j.demeyer@gmail.com>
From: Daan De Meyer <daan.j.demeyer@gmail.com>
Date: Thu, 12 Oct 2023 10:52:13 +0200
> Changes since v1:
>
> * Added missing Signed-off-by tag
You can put these after --- so that it will disappear when merged.
>
> We should not run the recvmsg() hooks on unnamed sockets as we do
> not run them on unnamed sockets in the other hooks either. We may
> look into relaxing this later but for now let's make sure we are
> consistent and not run the hooks on unnamed sockets anywhere.
>
> Signed-off-by: Daan De Meyer <daan.j.demeyer@gmail.com>
> ---
> net/unix/af_unix.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index e10d07c76044..81fb8bddaff9 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -2416,9 +2416,10 @@ int __unix_dgram_recvmsg(struct sock *sk, struct msghdr *msg, size_t size,
> if (msg->msg_name) {
> unix_copy_addr(msg, skb->sk);
How is an unnamed socket set to skb->sk ?
>
> - BPF_CGROUP_RUN_PROG_UNIX_RECVMSG_LOCK(sk,
> - msg->msg_name,
> - &msg->msg_namelen);
> + if (msg->msg_namelen > 0)
> + BPF_CGROUP_RUN_PROG_UNIX_RECVMSG_LOCK(sk,
> + msg->msg_name,
> + &msg->msg_namelen);
> }
>
> if (size > skb->len - skip)
> @@ -2773,9 +2774,10 @@ static int unix_stream_read_generic(struct unix_stream_read_state *state,
> state->msg->msg_name);
> unix_copy_addr(state->msg, skb->sk);
>
> - BPF_CGROUP_RUN_PROG_UNIX_RECVMSG_LOCK(sk,
> - state->msg->msg_name,
> - &state->msg->msg_namelen);
> + if (state->msg->msg_namelen > 0)
> + BPF_CGROUP_RUN_PROG_UNIX_RECVMSG_LOCK(sk,
> + state->msg->msg_name,
> + &state->msg->msg_namelen);
>
> sunaddr = NULL;
> }
> --
> 2.41.0
>
next prev parent reply other threads:[~2023-10-12 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 8:52 [PATCH bpf-next v2] Only run BPF cgroup unix sockaddr recvmsg() hooks on named sockets Daan De Meyer
2023-10-12 18:11 ` Kuniyuki Iwashima [this message]
2023-10-16 18:33 ` Martin KaFai Lau
2023-10-16 18:47 ` Kuniyuki Iwashima
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=20231012181142.60636-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=bpf@vger.kernel.org \
--cc=daan.j.demeyer@gmail.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
/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